Arvid Norberg
Arvid Norberg
> So creating a hybrid torrent from a v1-only torrent will not follow the hybrid torrent standard since the pieces are not padded. You can however create a v2-only torrent...
I'm not representing the tribler project (but one of its dependencies). Last time I downloaded the haiku-os alpha, it no longer came with GCC4 (just GCC2.95). I had libtorrent work...
alright, I did. libtorrent (master branch) builds and runs on Haiku now. (apparently I had misunderstood ``create_area()``, which I was using for page-aligned allocations)
thanks for the report. This is an old issue that I have not yet understood the cause of. I've spent a fair amount of time on it already. Perhaps it's...
I believe this is related https://github.com/arvidn/libtorrent/pull/7545
I believe the `RC_2_0` branch builds as C++20 (but with some warnings)
I believe this behavior is by design. silently ignoring disk errors is risky. The way you resume from a disk error (or any error to a torrent) is to call...
although, I agree that during the checking of files on disk it makes sense to be very tolerant of files being shorter than expected, for instance.
my understanding is that there are two kinds of tables in the wallet DB: 1. Tables that are built by syncing with the chain (and can be re-created by re-syncing...
it seems reasonable to leave unknown tables in the database. The case where we downgrade and resync, we're syncing with the old version anyway, the unknown tables won't interfere with...