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

BUG: Last submitted proposal not showing #13

Open
petersalomonsen opened this issue Jan 6, 2025 · 4 comments
Open

BUG: Last submitted proposal not showing #13

petersalomonsen opened this issue Jan 6, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@petersalomonsen
Copy link
Collaborator

Navigating to https://near.social/devhub.near/widget/app?page=proposals

The last visible proposal is number 298, even though I just submitted number 299 https://near.social/devhub.near/widget/app?page=proposal&id=299

Image

Acceptance criteria:

  • Make sure there is a test that checks the scenario of adding new proposals and reproduces the current observed issue
  • Fix the issue, and make sure that the test now verifies that new proposals are added to the index
@petersalomonsen petersalomonsen added the bug Something isn't working label Jan 6, 2025
@petersalomonsen
Copy link
Collaborator Author

@Tguntenaar Just observed this, so let's make sure we have a proper test for it.

@petersalomonsen
Copy link
Collaborator Author

I also observed that after some time, it is now visible. So if this is the intended behaviour, then I guess we need to inform the user about it in some way.

@Tguntenaar
Copy link
Collaborator

@petersalomonsen Hmm, what is some time exactly? We are at the mercy of the speed of nearblocks, we might be able to speed up something by posting an update request that uses the RPC's.

It showed 299 because of id 0. So it wasn't indexed probably.

@petersalomonsen
Copy link
Collaborator Author

@petersalomonsen Hmm, what is some time exactly? We are at the mercy of the speed of nearblocks, we might be able to speed up something by posting an update request that uses the RPC's.

It showed 299 because of id 0. So it wasn't indexed probably.

It must have been like 5 minutes delay ( since I had the time to write this report and the issue was still there ).

Yes let's start by reproducing the scenario in a test, before trying to fix it ( so that we don't spend a lot of time trying different solutions without seeing the real issue ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🆕 Triage
Development

No branches or pull requests

2 participants