Repository navigation
chore: update subxt + jsonrpsee - #422
Conversation
This fixes a potential stall in the RPC connection which could lead to the rest-api not reconnecting to the RPC servers.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
TarikGul
left a comment
There was a problem hiding this comment.
Checked this out and ran it rather than just reading the diff.
Pure dependency move, no source changes: subxt 0.51.0 to 0.51.1, jsonrpsee 0.24.10 to 0.26.1, and the lockfile. Builds clean, fmt and clippy clean, all unit suites green.
Smoke tested against a live node: /blocks/head, /blocks/{id}, /transaction/material, /transaction/parse, /transaction/fee-estimate and /pallets/staking/progress all 200, plus 40 sustained polls with no failures and nothing over 5s.
One thing I checked so it does not get blamed on this bump: /transaction/dry-run returns 400 on a historical signed extrinsic, but the currently deployed build returns a byte identical 400 for the same input, so that is pre-existing and worth its own look rather than holding this up.
Approving. Merging as soon as Integration Tests lands, then folding this into the open release PR so it goes out together with what is already queued there.
This fixes a potential stall in the RPC connection which could lead to the rest-api not reconnecting to the RPC servers.