Skip to content
This repository has been archived by the owner. It is now read-only.

Detect and don't attempt to recover from PoisonError #345

Merged
merged 1 commit into from Aug 7, 2019

Conversation

@tony-iqlusion
Copy link
Contributor

@tony-iqlusion tony-iqlusion commented Aug 7, 2019

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.

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.
@tarcieri tarcieri merged commit 30c2ae3 into master Aug 7, 2019
1 check passed
Loading
@tarcieri tarcieri deleted the exit-on-poison-error branch Aug 7, 2019
@tony-iqlusion tony-iqlusion mentioned this pull request Aug 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants