This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Trap exceptions thrown within run_in_background #3144
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not completely convinced about this, and #3138 might make it redundant anyway; however:
It strikes me that there are two common usecases for run_in_background:
In either case, it feels like having synchronous exceptions propagate outside run_in_background is unexpected. It feels better to have them turned into Failures so that they can either be handled by the defer.gatherResults(), or logged as unhandled errors for the background thread.