More verbose crashes
There are several instances, where one can get the m3
server to crash or not reply to the user at all. I don't mind the crashes too much — since they are mostly caused by inproper usage — but reporting to the user that something went wrong (and what went wrong) seems crucial to me.
My aim with this issue is to polish up 80% of the outstanding problems with about 20% work. I don't mind getting my fingers dirty myself, either. If you have some specific pointers for me, where to poke, I'll be happy to hear @fkosmale! If fixing these issues seems like to much work, I'd be absolutely happy with a wits-end error message saying The m3 server worker crashed. Are you sure you are running tinyPseuco code?
.
Currently I am observing these issues:
-
asserting writeValueSet to some program initialization throws writeValueSet
is not supported, though I thought it was...? . As a consequence, the UI gets thrown in a very odd state where said assertion can not be interacted with anymore. -
providing certain illegal tinyPseuco instructions, such as declarations as string z = "";
, appear to pass the parser, but don't report back to the server, as the Future throws an exception that is not caught. I'd prefer to catch these kinds of exceptions and report to the user that (something, eg.) parsing went wrong.
Edited by Felix Freiberger