Charles Kerr

I've been thinking about this one again ... @reardonia has done a lot of good patches and that sweat equity makes me look on this idea more favorably. So does...

The relevant part of bep 15: > Which format [ipv4 vs ipv6 addresses] is used is determined by the address family of the underlying UDP packet. I.e. packets from a...

Ideally this should be fixed before 4.0.0 which is coming out in a few days. If we wait longer than that for 4.0.0 then the project may miss Debian's freeze....

You know what, I think the last comment answers its own question. 4.0.0 has been in the works for like 18 months now; I shouldn't do anything that could introduce...

This issue was auto-closed when #4723 was merged. I'm re-opening it now for the bigger fix of supporting both ipv4 and ipv6 udp announces

Re-tagging this bug as a feature again now that we're in the "also support udp6 announces" phase

It's a timing issue in the test, so FWIW I don't think it's something breaking in production code. Still needs to get fixed though.

https://www.bittorrent.org/beps/bep_0027.html > When generating a metainfo file, users denote a torrent as private by including the key-value pair "private=1" in the "info" dict of the torrent's metainfo file [[1]](https://www.bittorrent.org/beps/bep_0027.html#bep-3).

> Totally speculative, but could be from #4696: you had an exception raised which caused some thread/view to crash but got recreated somehow. That change isn't in 4.0.0-beta.3 though?

Is this still an issue in 4.0.1?