In 0.3.11, when I would (as usual) run some idiotic code with lots of typos in it, I'd be flooded with error messages from all workers. Now, on 0.4, I am often puzzled by weird results, which I can trace down after a while to the fact that some arrays that should contain results are actually empty, because of errors happening on the worker processes.
In fact, I can do a remotecall_fetch() to verify that the workers produce errors, but when I run a loop in which the erroneous function is being called, the errors are just being passed over silently. Is this expected? Is there a way to change this behaviour?
