Planner not showing compiler errors (just IMP blinks green than red)

Squirrel Code
1

It seems one of the latest changes “disabled” in some case the compilation error.

How to reproduce: load a code which has an error on it - it happened for me with not initialised variable but in other cases too (bad constructor parameter list, etc.)
Example:
cs_pin = 0;//forgot to set cs_pin = hardware.pin2
than called
cs_pin.write or read

No error was shown in the planner neither at log, neither on Errors tab but the imp had three green blink than 2-3 fast red ones and kept rebooting. Till I got back to a blank code which doesn’t produced this behaviour.

Than started to put back my code line by line revealed my mistake but this kind of line by line development after every mistake is a real pain. Please fix this asap … Might be due to latency like was last time with logging since rarely I got error message so might not happen for everyone but it certainly does for Europe based developers …

2

I’m planning to push release-9 today, which improves error reporting significantly. Stay tuned!

3

Release-9 does not fixed anything - the error still not visible at all for higher latency connection programmers like I am from Europe. All I can see is impee going from online to offline, two red blinks and than restarting - no error displayed in Errors log or it’s displayed one from ten restarts. Refresh does not displays the error (like it was in the server.log latency issue).

It’s a pain to develop anything till this is not fixed so please do something - we can’t make our internet faster across the ocean …

4

Sometimes the last logs before error are missed too (which makes work even harder since not even server.log can be used to see which line of the code is reached).

Here it is one example log which has error somewhere after first line of code (first line is imp.configure, than a server log with “Test firmware starting …” than some code which has error in it:
Tuesday, November 13, 2012 12:54:14: Device configured to be "Test firmware"
Tuesday, November 13, 2012 12:54:14: Power state: online=>offline
Tuesday, November 13, 2012 12:54:25: Power state: offline=>online
Tuesday, November 13, 2012 12:54:25: Device booting
Tuesday, November 13, 2012 12:54:26: Device configured to be "Test firmware"
Tuesday, November 13, 2012 12:54:26: Test firmware starting …
Tuesday, November 13, 2012 12:54:26: Power state: online=>offline
Tuesday, November 13, 2012 12:54:41: Power state: offline=>online
Tuesday, November 13, 2012 12:54:42: Device booting
Tuesday, November 13, 2012 12:54:42: Device configured to be "Test firmware"
Tuesday, November 13, 2012 12:54:42: Power state: online=>offline
Tuesday, November 13, 2012 12:54:53: Power state: offline=>online
Tuesday, November 13, 2012 12:54:53: Device booting
Tuesday, November 13, 2012 12:54:55: Device booting
Tuesday, November 13, 2012 12:54:55: Device configured to be "Test firmware"
Tuesday, November 13, 2012 12:54:55: Test firmware starting …
Tuesday, November 13, 2012 12:54:55: Power state: online=>offline
Tuesday, November 13, 2012 12:55:06: Power state: offline=>online
Tuesday, November 13, 2012 12:55:06: Device booting
Tuesday, November 13, 2012 12:55:06: Device configured to be "Test firmware"
Tuesday, November 13, 2012 12:55:06: Test firmware starting …
Tuesday, November 13, 2012 12:55:06: Power state: online=>offline
Tuesday, November 13, 2012 12:55:17: Power state: offline=>online
Tuesday, November 13, 2012 12:55:17: Device booting

My hint would be: the error reporting cuts the connection too fast and the last messages + the error never reaches the planner.

5

Yep, this seems like the case. Looking at the issue now.

6

This should be fixed in release-11. Let me know if it still isn’t working for you.