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.

Sign up for GitHub

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

Jump to bottom

view-account-summary method doesn't work on testnet network #431

Closed
frolvanya opened this issue Dec 23, 2024 · 1 comment · Fixed by #433
Closed

view-account-summary method doesn't work on testnet network #431

frolvanya opened this issue Dec 23, 2024 · 1 comment · Fixed by #433
Assignees
@akorchyn
Labels
bug Something isn't working

Comments

@frolvanya
Copy link
Contributor

image

view-account-summary is crashing constantly during getting the staked balance. I'm not sure why it happens since testnet only has 28 nodes of validators compared to 500+ on mainnet, but I assume it can be fixed by splitting all validators by smaller chunks and process them one by one with a small delay in-between. If this won't help, let's at least display all other information that we can like social, native account balance, storage used and number of access keys
@frolvanya frolvanya added the bug Something isn't working label Dec 23, 2024
@github-project-automation github-project-automation bot moved this to NEW❗ in DevTools Dec 23, 2024
@akorchyn akorchyn self-assigned this Dec 23, 2024
@akorchyn akorchyn linked a pull request Dec 23, 2024 that will close this issue
bugfix: handle new rate-limits for querying pools #433
Merged
@akorchyn akorchyn mentioned this issue Dec 23, 2024
Merged
@akorchyn
Copy link
Collaborator

@frolvanya, invite you to review #433 :)

akorchyn added a commit that referenced this issue Dec 25, 2024
@akorchyn
bugfix: handle new rate-limits for querying pools (#433)
366c3ee 
Closes: #431 

* Added fast-near for testnet
* Rate limited querying pools to 140 / 30s

Ideally, if Fastnear is stable enough, the user shouldn't be able to hit
this limit as we will query information within the pools the user has
staked before.
But in case the fastener fails, we would need to query all active pools,
which number more than 150.

| Network | FastNear | Non fast near |
| :---:   | :---: | :---: |
| Testnet | < 140 (mostly 0-5) | 563 pools 
| Mainnet | < 140 ( mostly 0-5 ) | State of contract poolv1.near is too
large to be viewed |

@race-of-sloths
@github-project-automation github-project-automation bot moved this from NEW❗ to Shipped 🚀 in DevTools Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akorchyn akorchyn

Labels
bug Something isn't working
Projects
DevTools
Status: Shipped 🚀
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bugfix: handle new rate-limits for querying pools near/near-cli-rs
2 participants
@akorchyn @frolvanya