unstable rpc backend: `best_block` or `all_blocks` subscription may be silently lose blocks when reconnecting
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
It's possible that blocks may be be silently missed if a reconnecting occurs because it's restarted by unstable backend.
For instance the following could happen:
- A connection is established
- Block A, Block B, and Block C are announced and propagated in the subscription
- The connection is lost and during this phase Block D is announced
- Then after a while the connection is re-established and the next Block E is announced.
Thus, Block D is missed and no way to now about it.
Because subxt mainly care about that finalized blocks, it's not critical for now.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the RPC subscription and reconnect handling described by the issue; no file or test entry point is provided. Done means reconnecting subscriptions no longer silently omit an announced block, with the A–E sequence covered or the limitation explicitly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100