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 · 4 comments
Closed

/v2/info only updates on burn block #4351

obycode opened this issue Feb 7, 2024 · 4 comments
Assignees

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 added a commit that referenced this issue Feb 8, 2024
@saralab saralab closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants