Arvid Norberg
Arvid Norberg
this is an issue when writing (and extending) files via memory mapped files. All disk I/O errors are reported as a very small number of signals (or structured exceptions on...
When using memory mapped files, errors are reported via signals, and so don't have high fidelity. There is some heuristics in libtorrent to guess whether the error is actually out-of-space...
> Personally it's preferable to keep them separate since you often want to validate transactions, compute the cost, or unit test them without actually having valid signatures Yeah, there are...
you might want to rebase on top of `refactor-get-block-generator` in advance, to make sure it's a clean merge
are you using the C bindings?
`write_uint16()` (which is a wrapper around `write_impl()`) prints the bytes in network byte order. See the implementation [here](https://github.com/arvidn/libtorrent/blob/RC_2_0/include/libtorrent/aux_/io.hpp#L68-L79). It shifts right by 8 and masks with `0xff` for the first...
I will investigate the logic and get back to you. I agree that libttorrent does not appear to implement the BEP correctly. Regarding the endianness, both the pointer and span...
thanks for the report! It's addressed here https://github.com/arvidn/libtorrent/pull/7743
they are here: https://github.com/Chia-Network/chia-blockchain/blob/main/chia/consensus/constants.py#L33-L46
perhaps it's sufficient to just set this one constant in the override config then, and the current logic might already override the other variants