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

/v2/info only updates on burn block #4351

Closed
obycode opened this issue Feb 7, 2024 · 5 comments
Closed

/v2/info only updates on burn block #4351

obycode opened this issue Feb 7, 2024 · 5 comments
Assignees
Labels

Comments

@obycode
Copy link
Contributor

obycode commented Feb 7, 2024

In running the managed testnets, we realized that the /v2/info endpoint does not stay up-to-date with the current Stacks tip height. Instead it is only updating when a new burn block is processed.

@jcnelson
Copy link
Member

jcnelson commented Feb 7, 2024

Yup, that's the current design.

@jcnelson
Copy link
Member

jcnelson commented Feb 7, 2024

You can fix it by checking the canonical stacks tip instead of the burnchain tip when determining whether or not the state for /v2/info needs to be reloaded. Unfortunately I'm too behind on the network state machines to do this right this second, but if you don't feel comfortable doing it, I can fold it into one of the PRs.

@obycode
Copy link
Contributor Author

obycode commented Feb 7, 2024

Yup, I can take this one when I have some time.

@jcnelson jcnelson self-assigned this Feb 8, 2024
jcnelson added a commit that referenced this issue Feb 8, 2024
@jcnelson
Copy link
Member

jcnelson commented Feb 8, 2024

PR sent

@jcnelson jcnelson moved this from Status: 🆕 New to Status: In Review in Stacks Core Eng Feb 8, 2024
jcnelson added a commit that referenced this issue Feb 8, 2024
@saralab saralab moved this from Status: In Review to Status: ✅ Done in Stacks Core Eng Feb 8, 2024
@saralab saralab closed this as completed Feb 8, 2024
@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
Development

No branches or pull requests

4 participants