Skip to content

Rethrow exceptions from forked threads in bye #478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

FinleyMcIlwaine
Copy link
Contributor

See commit c05ce0eb2c1adb3e29a5a95783f43fa8ed59162e message. That was motivated by the forked threads in bye printing their exceptions to stdout. However, those changes may mask exceptions occurring in bye that we actually care about. This commit fixes that by leaving exceptions in bye uncaught, and simply rethrowing exceptions that occur in the forked threads of bye back to the main thread. No messages printed to stdout, but potentially important exceptions are still propagated.

See commit `c05ce0eb2c1adb3e29a5a95783f43fa8ed59162e` message. That was
motivated by the forked threads in `bye` printing their exceptions to stdout.
However, those changes may mask exceptions occuring in `bye` that we actually
care about. This commit fixes that by leaving exceptions in `bye` uncaught, and
simply rethrowing exceptions that occur in the forked threads of `bye` back to
the main thread. No messages printed to stdout, but potentially important
exceptions are still propagated.
@edsko
Copy link
Contributor

edsko commented Oct 4, 2024

Obsoleted by #477 (comment) .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants