bitshares / bitshares/bitsharesjs-ws
Terminating a ws connection takes forever, why?
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 121
- Avg merge
- 7h 10m
- Merged PRs (30d)
- 1
Description
I am testing new reconnection strategy for UI and I found that it takes forever when ChainWebSocket recognizes that connection is dead until the rpc_connection_status in BlockchainStore is updated.
Why is that @svk31 ? You can test it by simply opening the UI and disabling the internet connection after connection has been established. Are there any timeouts involved that are possibly to high?

Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue in the UI by disabling internet access after the connection is established. Trace how ChainWebSocket recognizes the dead connection and how BlockchainStore updates rpc_connection_status; done means the status changes promptly after the connection is lost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100