This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Deadlock when using RPCs #4339
Labels
F0-consensus 💣
Issue can lead to a consensus failure.
M4-core ⛓
Core client code / Rust.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone
Comments
gavofyork
added
F0-consensus 💣
Issue can lead to a consensus failure.
M4-core ⛓
Core client code / Rust.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
labels
Jan 28, 2017
gavofyork
added
F0-consensus 💣
Issue can lead to a consensus failure.
and removed
F0-consensus 💣
Issue can lead to a consensus failure.
labels
Jan 28, 2017
another one where syncing continued but the WS stopped. in this case it wasn't a hard lockup; just that new WS connections (and thus the entire UI) failed. client stopped on SIGTERM as usual.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F0-consensus 💣
Issue can lead to a consensus failure.
M4-core ⛓
Core client code / Rust.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
The text was updated successfully, but these errors were encountered: