diff options
| author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-10-08 10:41:58 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-10-08 10:42:04 +0200 |
| commit | df50fd194fb804edba8a513b1eb699de38ca3963 (patch) | |
| tree | 64ee0dfa24851c502a5c7c0bf41e5ab7670b7ed7 /build_msvc | |
| parent | 866fd2888f42f8d81e3b1ab5eb647c86102158ac (diff) | |
| parent | 3284e6c09a84e9557ec72723ad636053d3ef7122 (diff) | |
Merge #16802: scripts: In linearize, search for next position of magic bytes rather than fail
3284e6c09a84e9557ec72723ad636053d3ef7122 scripts: search for next position of magic bytes rather than fail (Tim Akinbo)
Pull request description:
When using the `linearize-data.py` contrib script to export block data, there are edge cases where the script fails with an `Invalid magic: 00000000` error. This error occurs due to the presence of padding bytes that occasionally appears between consecutive blocks in the block data file.
There's an ongoing conversation about this in #14986. sipa also admitted that it is a bug in #5028. Fortunately, this is not an issue in bitcoin core as it handles this type of situation gracefully and so no fix in bitcoin core is required.
This PR is an improvement on how the script handles these "invalid magic bytes". Rather than failing, this patch allows the script to search for the next occurrence of the magic bytes and then starts reading the block from there.
ACKs for top commit:
laanwj:
ACK 3284e6c09a84e9557ec72723ad636053d3ef7122
Tree-SHA512: 18067ae0b4b62e822dfc558a86439ad6acaf939b98479e38e8e4248536574643b26eb48e96ec7139375c88b42cbe7705a64deb13a3c239e16025a6aad3d69bfa
Diffstat (limited to 'build_msvc')
0 files changed, 0 insertions, 0 deletions