Improved error reporting on comms

[philippjfr]

Improves the traceback reported in the console on error by including filename, error type, line number and function.

[jlstevens]

I'm very happy with this, especially as everything stays simple on the Javascript side.

My only comments:

• Capture needs a docstring to explain why it is needed - to capture stdout (e.g print output) and make it available on the web console for debugging etc.
• It probably wouldn't be too hard to capture stderr at the same time and I would consider doing this for consistency.
• Lastly, I might consider renaming Capture to something like StandardOutput. Then the context manager can be used with:

with StandardOutput() as stdout:
     ...
if stdout: ... 

You'll need two context managers if you want to also handle stderr - at least if you want to continue using each one inheriting from list:

with StandardOutput() as stdout, StandardError() as stderr:
     ...
if stdout: ...
if stderr: ... 

The redundancy between the StandardOutput and StandardError context managers is a little annoying but maybe you could parameterize it to have StandardIO('stdout)' and StandardIO('stderr')...

[jlstevens]

Great, tests are passing! Merging.

[jlstevens]

I know this PR is merged now but I want to just state one thing that is still niggling at me. How will a regular user even know the check the Javascript console for messages? Both of us know that the output is going there now but it is invisible to everyone else until they look at the docs to find out.

Not sure how best to handle this. Javascript alerts would be very obvious, but also very annoying...though maybe for stdout, using alerts might make sense even if exceptions don't?

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.