-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot see I2P peers #18926
Comments
@absolutep As I mentioned in #18922 (comment) @glassez has created a PR #18845 to resolve this issue but it hasn't been merged yet. The reason is mentioned/indicated in #18921 (comment) Basically, if that PR was merged - it would break our CI Environment as the Again, a custom build would need to be provided to you inclusive of PR #18845 or you'll have to wait for official libtorrent releases EDIT: |
@absolutep I've created another custom build with PR #18845 for you below: Please note that only 1 build is available/successful (2.0.x), the libtorrent (1.2.x) build failed.....I can't invest much more time in investigating it. @glassez You may be interested in the failure.... |
Latest I2P related changes were not backported to 1.2.x branch. And I'm not sure they will. So we will have to conditionally exclude support for I2P in case when qBittorrent is built with libtorrent-1.2. |
Thank you very much @xavier2k6 |
If possible @glassez please consider pushing this build for general public release. |
You're more than welcome, if you notice any other issues with I2P support please feel free to feedback. |
This needs to be taken care of for next release.
|
Currently, this beta release seems to have solved the issue = #19066 (comment) As shown here = #19066 (comment) |
qBittorrent & operating system versions
What is the problem?
No peers can be seen in qBittorrrent for I2P torrents.
Other I2P supported torrent clients can see qBittorrent peers. As shown in screenshots.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: