greg/mentat

[core] Handle poisoned Mutex in top-level Conn #142

New issue

Open

opened 2020-08-06 16:55:37 +00:00 by gburd · 0 comments

gburd commented

2020-08-06 16:55:37 +00:00

(Migrated from github.com)

This is follow-up to #342, per https://github.com/mozilla/mentat/pull/342#discussion_r103071273. It is likely that the best we can do is close and re-open. If we do clever things like #129, there might be additional journal/integrity checking to juggle here.

This is follow-up to #342, per https://github.com/mozilla/mentat/pull/342#discussion_r103071273. It is likely that the best we can do is close and re-open. If we do clever things like #129, there might be additional journal/integrity checking to juggle here.

Sign in to join this conversation.

No labels

good first issue

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/mentat#142

No description provided.