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: Respond to getblockchaininfo requests when the state is empty #8939

Closed
arya2 opened this issue Oct 16, 2024 · 1 comment · Fixed by #9138
Closed

bug: Respond to getblockchaininfo requests when the state is empty #8939

arya2 opened this issue Oct 16, 2024 · 1 comment · Fixed by #9138
Labels
C-bug Category: This is a bug lightwalletd any work associated with lightwalletd S-needs-triage Status: A bug report needs triage

Comments

@arya2
Copy link
Contributor

arya2 commented Oct 16, 2024

Lightwalletd test failed when calling getblockchaininfo in #8857.

This looks like a bug where Zebra, when its state is empty, should be using the known genesis block height, hash, and time or responding without some fields.

@arya2 arya2 added C-bug Category: This is a bug S-needs-triage Status: A bug report needs triage labels Oct 16, 2024
@github-project-automation github-project-automation bot moved this to New in Zebra Oct 16, 2024
@arya2 arya2 added the lightwalletd any work associated with lightwalletd label Oct 16, 2024
@elijahhampton
Copy link
Contributor

I opened a PR for this issue: https://github.com/ZcashFoundation/zebra/pull/9138/files

@mpguerra mpguerra linked a pull request Jan 20, 2025 that will close this issue
7 tasks
@mergify mergify bot closed this as completed in #9138 Jan 23, 2025
@github-project-automation github-project-automation bot moved this from New to Done in Zebra Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug lightwalletd any work associated with lightwalletd S-needs-triage Status: A bug report needs triage
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants