FIXED: listCOMP and errorDAT bugs

Bugs
1

Hi there,

I think I found two bugs.

Changing the rows or cols parameter in the listCOMP throws an cook dependency error.
I try to print errors with a listCOMP and this makes it kind of impossible.

Secondly saving the log of the errorDAT seams to be broken.

Cheers, David
listComp and errorDat bugs.toe (5.33 KB)

2

Hi David.

The first error we can reproduce and will look into a workaround or fix.

In terms of the second, what are you seeing?
It seems to be logging all info as well, including extension compilation info in /sys.
Perhaps it should be changed to skip /sys nodes by default.

Cheers,
Rob.

3

Hi Rob,

I was probably only confused by the ‘log current errors’ function.
It is probably working just fine.
Sorry about that.

Cheers, David

4

Okay cool.
I’ve gone ahead and fixed the recursion error in the meantime. (when changing rows/cols)
Cheers,
Rob

5

Awesome, looking fowrward to continue my error log listCOMP :smiley:

6

Hi there,

I made another attempt to make this work and stumbled upon another issue, which I demonstrated in the attachted file. When there is a file missing, that a textDAT is synced to, I get some kind of error loop in the errorDAT.

Best wishes,
David

Error Logger.2.toe (3.9 KB)

7

As mentioned here, should be fixed now for next build. FIXED: Problem with file syncing and error logging

1 Like