[bisq-network/bisq] Unhandled unrecoverable program state following failed seed handshake (#2549)
notifications at github.com
Sun Mar 17 04:05:43 UTC 2019
Related to: #2547, possibly #2474, #2327
This is a slightly edited re-post of the issue reported at:
After a network congestion/degradation during startup (issue #2547), Bisq remains in a dead-end state that doesn't recover even after the network performance is restored. The only way to recover is restarting the program.
This condition is not properly handled nor reported in the UI, causing confusion to unaware users.
**Steps to reproduce**
- same as issue #2547, start with a working installation
- close application
- degrade network: `sudo tc qdisc add dev eth0 root tbf rate 100kbit burst 1540 latency 50ms`
- start application
- wait 3 hours, per issue #2547 there should be no progress past step 3/4
- remove network degradation: `sudo tc qdisc del ...`
- wait indefinitely, there will still be no progress past step 3/4, even 12 hours later
The program should attempt to recover seamlessly from the degraded state when the network conditions allow it.
**Alternative expected result**
The program should detect the dead-end state and report it in the UI along with some information about its probable cause, then exit or restart in order to attempt to recover from this state.
The program keeps running and displays a progress indicator and shows the offers, trades, wallet contents, exchange rates etc, creating a false appearance of almost-operational and a false expectation of further progress, when in reality it is in an unrecoverable no-op state.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github