This repository has been archived by the owner on Jun 3, 2020. It is now read-only.
Detect and don't attempt to recover from PoisonError #345
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
PoisonError indicates that a mutex-guarded data structure is in an inconsistent state because a panic occurred while the mutex was held. We can't recover from these, so detect when they happen and exit afterward. Additionally this names each client thread to ease debugging, and adds some better debug logging in several places.
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PoisonErrorindicates that a mutex-guarded data structure is in an inconsistent state because a panic occurred while the mutex was held.We can't recover from these, so detect when they happen and exit afterward.
Additionally this names each client thread to ease debugging, and adds some better debug logging in several places.