Repository navigation
Update workqueue abort message on concurrent access. - #8566
Merged
Merged
Conversation
This updates the error message when the workqueue threading layer has to abort due to concurrent access being detected. It now includes: * That it is Numba workqueue that is causing the `SIGABRT`. * The reason for the abort (concurrent access). * Common use cases that end up causing the problem. * What to try instead and the docs on how to do it. Fixes numba#8563
sklam
approved these changes
Nov 8, 2022
sklam
added
5 - Ready to merge
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This updates the error message when the workqueue threading layer has to abort due to concurrent access being detected. It now includes:
SIGABRT.Fixes #8563