Fix inconsistent node error state #731
Merged
+3
−1
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.
Fixes inconsistent node error state as described here #718 (comment)
The issue was that app status screen checked if node running AND synced without failure, but electrum config page check only if node is running.
When sync fails (timeout), the node is still running, so one screen showed error and the other showed connected.
Fix: Made both screens use the same logic - now electrum config also checks for sync errors before showing "Connected".