Hi, ------- Original Message ------- On Thursday, March 2nd, 2023 at 01:39, Barak A. Pearlmutter <ba...@pearlmutter.net> wrote: > Okay, I cherry-picked upstream commits 487cc27e1..d21a3b622, the > endpoint being the current upstream/main, and built, and installed, > and it seems to solve this problem. The "no bencoded data to parse" > messages are gone. And things verify upon request, with most of them > succeeding.
Since we missed the freeze anyway, I'd suggest we give upstream a couple more days for a release including the fixes? > A few failed to verify even though they are absolutely > downloaded; these are all single file torrents, instead of a directory > containing files. So that's a clue as to the bug, I suppose. What does "fail to verify" mean? Does it invalidate the whole download? Or are they stuck in some state? My test upgrade triggered verifications for all existing torrents, but once verifications were done, all seemed good. Cheers Leo Antunes
