Setup UncaughtExceptionHandler for WorkerThread
#4233
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
djspiewak
reviewed
Jan 9, 2025
| pollingSystem: PollingSystem = SelectorSystem()) | ||
| : (WorkStealingThreadPool[_], pollingSystem.Api, () => Unit) = { | ||
| pollingSystem: PollingSystem = SelectorSystem(), | ||
| uncaughtExceptionHandler: Thread.UncaughtExceptionHandler = (_, ex) => |
There was a problem hiding this comment.
Why can't we just use reportFailure?
There was a problem hiding this comment.
reportFailure is for tasks that fail on the WSTP. uncaughtExceptionHandler is for when the WTs themselves fail, which is effectively fatal. Besides, the default reportFailure in IOApp schedules the printing on the runtime, which is a bad place to send failures about the runtime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #4232.