handle disconnection
Open
bug
ux
- Dominant language
- C++
- Stars
- 4
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
If api node gets offline for any reason gwallet will became unresponsive when executing next command.
Disconnection should be handled properly and request the user to reconnect/change api node.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Begin by locating the API-node connection and command-request handling, then reproduce the offline-node case. Done means the wallet remains responsive and asks the user to reconnect or change the API node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100