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

StargateClient.GetBalanceStaked for noble never fires the actual query (noble doesnt have staking module, but should still fire query, like neutron) #1594

Open
MbBrainz opened this issue Jun 7, 2024 · 0 comments

Comments

@MbBrainz
Copy link

MbBrainz commented Jun 7, 2024

Noble chain doesn't have staking module, and so the staking query is not going to work. However, For some reason, the query is not fired, nor does the function error, leading to vague errors (like infinite fetch loading in reactQuery).

In the case of Neutron, which also doenst have a staking module, the query would be fired and would return "code":6, log": "unknown query path: unknown request", ... from the rpc. This is easily handled and seems to be the expected way.

As the root cause of this issue is still to be found, ive recorded a loom with a detailed debug description: https://www.loom.com/share/86b6ac00e0934f3a888e0224a7371579?sid=9e6239de-11a3-4853-a5f1-2eab29c71e71

https://github.com/cosmos/cosmjs/blob/f71cdc35a815f76842055ab73b89b24428698527/packages/stargate/src/stargateclient.ts#L346-L368C4

@MbBrainz MbBrainz changed the title StargateClient.GetBalanceStaked for noble never fires the actual query because noble doesnt have staking StargateClient.GetBalanceStaked for noble never fires the actual query (noble doesnt have staking module, but should still fire query, like neutron) Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant