Skip to content
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

Handle Stale RPCs error for chains that have no RPCs #1153

Open
sentry-io bot opened this issue Nov 15, 2023 · 0 comments
Open

Handle Stale RPCs error for chains that have no RPCs #1153

sentry-io bot opened this issue Nov 15, 2023 · 0 comments
Labels
bug A bug

Comments

@sentry-io
Copy link

sentry-io bot commented Nov 15, 2023

Sentry Issue: TALISMAN-EXTENSION-TWP

We know that GM has no RPCs, so we either shouldn't attempt to subscribe to it, or at least this error shouldn't end up in Sentry as unhandled

I think the reason why it's unhandled is because it's thrown inside Promise.race:

This is a similar situation to the one faced here, although in this case it is an Error being thrown, which suggests that the method used in that commit will not work to fix that problem. We should make a minimal reproduction case of errors thrown inside advanced Promise methods to understand how these should be handled.

Error: No healthy RPCs available for chain gm
  at chainConnector.connectChainSocket (../../packages/chain-connector/dist/talismn-chain-connector.esm.js:899:13)
  at chainConnector.subscribe (../../packages/chain-connector/dist/talismn-chain-connector.esm.js:747:26)

Error: RPCs are stale/unavailable for chain gm
  at Error: RPCs are stale (/unavailable for chain gm)

This error is occurring in the Portal as well as the extension.

@chidg chidg added the bug A bug label Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug
Projects
None yet
Development

No branches or pull requests

1 participant