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

Staking page broken? #11061

Closed
bkchr opened this issue Nov 5, 2024 · 7 comments · Fixed by #11063
Closed

Staking page broken? #11061

bkchr opened this issue Nov 5, 2024 · 7 comments · Fixed by #11063
Assignees
Labels
Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. P0 - Urgent Highest priority, critical to project success. Needs immediate resolution to prevent delays.

Comments

@bkchr
Copy link

bkchr commented Nov 5, 2024

image

It only shows 0/500 validators. When opening the page it first showed 499/500, but then switched to 0. Also the list of validators is not loading. The ERA information on the right side also looks like something is off?

@TarikGul TarikGul added P0 - Urgent Highest priority, critical to project success. Needs immediate resolution to prevent delays. Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. labels Nov 5, 2024
@TarikGul TarikGul self-assigned this Nov 5, 2024
@TarikGul
Copy link
Member

TarikGul commented Nov 5, 2024

Okay so the source of the issue seems to be this upstream PR in the api: polkadot-js/api#5997

Looking into it!

@radiumb
Copy link
Contributor

radiumb commented Nov 5, 2024

FYI the issue is seen in kusama staking page too so probably many other chains too

@TarikGul
Copy link
Member

TarikGul commented Nov 5, 2024

This would affect every staking page. We found the source of the issue - going to add it to the api then apply the changes here.

@radiumb
Copy link
Contributor

radiumb commented Nov 5, 2024

Wonderful, we came across this issue when we were doing some infrastructure upgrades and noticed this issue with our endpoint as a part of our qualification steps. We first worried it was something on our end but then noticed its pervasive and rpc provider agnostic hence pinged @bkchr .

@TarikGul
Copy link
Member

TarikGul commented Nov 5, 2024

Nice, well thank you for identifying. As back story we discovered some long standing memory issues as part of the RPC infrastructure in PJS as part of some tech debt. So we are aiming to improve it - there was one issue with the default capacity that was applied in the rpc-core in the api. So as a patch I am going to increase it but then also add an api option to increase it based on the client or users needs (basically an escape hatch)

@TarikGul
Copy link
Member

TarikGul commented Nov 5, 2024

This is fixed, and pushed to polkadot.js.org/apps

@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Nov 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. P0 - Urgent Highest priority, critical to project success. Needs immediate resolution to prevent delays.
Development

Successfully merging a pull request may close this issue.

4 participants