Script doesn’t terminate
complete
Peter Hilton
My script doesn't complete within 30-60 seconds, while the same input and script runs in less than a second with
node
on the command line.This isn't too surprising, because I’m using Advent of Code to practice map, filter and reduce, and my day 2 solution isn't trying to be time or space efficient (although it’s not _that_ bad).
It would be nice to get an error if it isn't going to complete in a reasonable amount of time.
T
Tom Dawes
complete
We've added a progress bar (of sorts) that should give you a bit more information about what's going on. Infinite loops will still be infinite, but hopefully that's a start :-)
(We're also improved the performance a lot, so hopefully your code will finish a lot quicker now!)
T
Tom Dawes
planned
T
Tom Dawes
Hi Peter,
Thanks for your feedback!
We're aware of the performance issues when running on the larger AoC input, and have come up with a few ways to improve execution speeds (a couple have been implemented already, and hopefully we'll get the rest out by the end of the day).
We'd also like to improve what we display while code is executing (e.g. the different stages of our pipeline), which will hopefully give you a better idea of how long it might take to finish.
Unfortunately, we can't really predict how long the code itself will take to execute. We could show something once the execution hits a certain duration (e.g. 20s) so that you know it's still running and hasn't crashed, if that sounds useful?
Thanks,
Tom
Tom Renner
Tom Dawes: I'd say a "not crashed" indicator would be useful, yes - especially for beginners who are likely to be less used to computers taking more than a second or two for a task.
Really liking the tool!