paritytech / paritytech/subxt

reconnecting rpc: ensure poll order to avoid outdated subscription ID on reconnect

Open
#1,567 1 comment 0 reactions 1 assignee View on GitHub

@pkhry is already working on this.

Since May 24, 2024.

Dominant language
Rust
Stars
489
Forks
293
Avg merge
18h 35m
Merged PRs (30d)
3

Description

Originally posted by @lexnv in https://github.com/paritytech/subxt/pull/1505#discussion_r1584924860

TLDR, when a re-connection occurs the poll order of "pending futures" should wait until chainHead__follow returns then fetch the updated subscription ID.

Currently we have a hack to retry these a calls a few times.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.