We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes when the Chainhook service receives a new_burn_block, it then fails to download the block.
new_burn_block
I'm not entirely sure why this happens, as the same block will be downloaded (at pretty much the exact same time) by Ordhook.
But, when this does happen, because we have a gap in our fork pool, we fail to append all future bitcoin blocks. We should:
The text was updated successfully, but these errors were encountered:
fix: shut down observer on bitcoin block download failure (#573)
907bf56
Fixes #572
f3530b7
chore(release): 1.6.0 [skip ci]
adda6ec
## [1.6.0](v1.5.1...v1.6.0) (2024-05-09) ### Features * add Bitcoin transaction index to typescript client ([#568](#568)) ([6f7eba4](6f7eba4)) ### Bug Fixes * add stacks event position to ts client ([#575](#575)) ([3c48eeb](3c48eeb)) * add starting stacks height for prometheus metrics ([#567](#567)) ([6a8c086](6a8c086)) * make bitcoin payload serialization deserializable ([#569](#569)) ([5f20a86](5f20a86)) * set `Interrupted` status for streaming predicates that fail ([#574](#574)) ([11bde53](11bde53)), closes [#523](#523) * shut down observer on bitcoin block download failure ([#573](#573)) ([f3530b7](f3530b7)), closes [#572](#572)
🎉 This issue has been resolved in version 1.6.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Sorry, something went wrong.
MicaiahReid
Successfully merging a pull request may close this issue.
Sometimes when the Chainhook service receives a
new_burn_block
, it then fails to download the block.I'm not entirely sure why this happens, as the same block will be downloaded (at pretty much the exact same time) by Ordhook.
But, when this does happen, because we have a gap in our fork pool, we fail to append all future bitcoin blocks. We should:
The text was updated successfully, but these errors were encountered: