-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic upon establishing client connection #1171
Comments
Hey Oliver, Subxt is expecting the Indeed for some custom chains, this assumption might not hold true. I'm wondering are you targeting a live-chain or a local-node? 🤔 To avoid the panic, I believe we could extend generate_runtime_error_type() |
I'm curious to know when a The code to reproduce basically extracts endpoints from https://github.com/polkadot-js/apps/blob/master/packages/apps-config/src/endpoints/productionRelayPolkadot.ts and then tries to build a client from each of them, so I guess that one of those is missing a |
The following url was causing the panic Inspecting the metadata of that chain concluded that the
As such have created a PR that:
Idem for Thanks again Oliver for raising this! |
I am trying to connect to different nodes with the Subxt library and hit this panic when connecting to a specific node:
RuntimeCall exists in V14; qed
.Can you please make this an error instead of a panic so my program does not crash?
Stack trace
Code for reproduction is here: subquery.zip (just
cargo r
).The text was updated successfully, but these errors were encountered: