You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, it happens that the underlying RPC client used by Subxt disconnects (e.g. due to network issues). In this case, the client throws an error that is not easy to detect in subxt, see paritytech/subxt#1190.
This makes our client stuck in an infinite retry loop.
[2024-05-07T13:56:14Z INFO runner::runner] Error fetching executable: SubxtError: Rpc error: RPC error: The background task been terminated because: Networking or low-level protocol error: WebSocket connection error: connection closed; restart required. Retrying...
[2024-05-07T13:56:15Z INFO runner::runner] Error fetching executable: SubxtError: Rpc error: RPC error: The background task been terminated because: Networking or low-level protocol error: WebSocket connection error: connection closed; restart required. Retrying...
TODO
This PR adds a new experimental implementation of an RPC client that automatically reconnects. This implementation is only available in subxt v0.35 or later. I tried bumping the subxt dependencies we use in Spacewalk to that version but I encountered conflicts because our Polkadot dependencies are too outdated.
Once we update our polkadot dependencies to a later version, try bumping subxt to v0.35 or later and use the experimental RPC client implementation hidden behind the reconnecting-rpc-client feature of subxt.
The text was updated successfully, but these errors were encountered:
This unfortunately is blocked by yet another upgrade of our polkadot dependencies. We can probably only really work on this once we bump our dependencies to Polkadot v1.6.0, ie the next one after the upgrade to v1.1.0. @prayagd do we already have a ticket for the v1.6.0 upgrade? If so, let's indicate as a Zenhub dependency that this ticket is blocked by that.
Context
Sometimes, it happens that the underlying RPC client used by Subxt disconnects (e.g. due to network issues). In this case, the client throws an error that is not easy to detect in subxt, see paritytech/subxt#1190.
This makes our client stuck in an infinite retry loop.
TODO
This PR adds a new experimental implementation of an RPC client that automatically reconnects. This implementation is only available in subxt v0.35 or later. I tried bumping the subxt dependencies we use in Spacewalk to that version but I encountered conflicts because our Polkadot dependencies are too outdated.
reconnecting-rpc-client
feature of subxt.The text was updated successfully, but these errors were encountered: