Error line number and file for Interval Jobs

NateDog · Post by **NateDog** » 26 Jul 2006, 17:21

Seems then when an error is thrown and it a process that was invoked by an Interval, then the error reporting in the logs does not include the filename and line number where the error was thrown.

If this could be added it would greatly help with tracking and down those pesky bugs that seem to only come up once in a thousand transactions... thanks.

jflowers45 · Post by **jflowers45** » 04 Sep 2006, 07:03

This would be a HUGE help

Right now we get errors like "cannot read property length from undefined" which most likely means it's expecting an array but getting undefined. Problem is, that could be in tons of places!

jflowers45 · Post by **jflowers45** » 04 Sep 2006, 07:44

Although - in that particular case it's inside of a try/catch ... would be nice if "catch" could reference the file and line #

Post by **Lapo** » 04 Sep 2006, 16:03

Yeah, I see. I am putting this on top of our todo list... we'll try to add it asap

Post by **Lapo** » 05 Sep 2006, 09:33

A quick update to tell you that the problem has been fixed and you'll have better setInterval error handling in the next release

cheers