You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge #1601: fix(core): calling CheckPoint::insert with existing block must succeed
3ae9ecb test: fix off-by-one in `checkpoint_insert_existing` (valued mammal)
e6aeaea doc(core): document panic for `CheckPoint::insert` (valued mammal)
2970b83 fix(core): calling `CheckPoint::insert` with existing block must succeed (志宇)
Pull request description:
### Description
Previously, we were panicking when the caller tried to insert a block at height 0. However, this should succeed if the block hash does not change.
### Notes to the reviewers
For context:
* lightningdevkit/ldk-node#358
* https://discord.com/channels/753336465005608961/978744259693916230/1283050849429356629
### Changelog notice
* Fix `CheckPoint::insert` to not panic when inserting existing genesis block (same block height and hash).
### Checklists
#### All Submissions:
* [x] I've signed all my commits
* [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md)
* [x] I ran `cargo fmt` and `cargo clippy` before committing
#### Bugfixes:
~~* [ ] This pull request breaks the existing API~~
* [x] I've added tests to reproduce the issue which are now passing
ACKs for top commit:
ValuedMammal:
Self ACK 3ae9ecb
notmandatory:
ACK 3ae9ecb
Tree-SHA512: 638d8aacac59ad18b5ee369d08f39bb12cc37fa9b3f936404b60dbf44938ef850ca341d00566840b5a77909d31c9291ab56299d986d832005ca96cd91a0b0e55
0 commit comments