-
Notifications
You must be signed in to change notification settings - Fork 9
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
/accounts/balance hangs #347
Comments
From #377:
And thanks for posting a simple command to test with. @protango Could I have you try on this branch? https://github.com/oasisprotocol/oasis-rosetta-gateway/tree/pro-wh/feature/delegations |
What is the alternative way to get escrow balance since it is still open issue and not resolved yet? |
I'd say patch out these lines https://github.com/oasisprotocol/oasis-rosetta-gateway/blob/v2.3.0/services/account.go#L151-L170 they take a long time to run, and they could time out if the node is too slow to answer in time. this should allow you to get the escrow balance if you don't need to get the detailed delegation info |
Hello @pro-wh I tried your comment by patching out code lines, |
can you open a new issue with some more information about this? the gateway uses the balance directly from the oasis-node. can you try getting the account info with the cli https://github.com/oasisprotocol/cli/ connected to that node? |
When I try without
It is balance response when adding |
that means no ROSE is delegated to that address. you need to put in the address of, for example, a validator to see the total ROSE delegated to it. |
Ah, Then how can I get delegator's escrow balance? |
unfortunately there's no fast way to do it in the 22.2.x oasis-node. there's only that slow piece of code that was timing out for you |
we've resolved this in oasis-core |
probably happens when we try to populate the detailed delegation records for our custom metadata.
we'll have to remove this because we don't currently have a way to retrieve this other than to brute-force loop over all delegations
cross reference #61 , #62
The text was updated successfully, but these errors were encountered: