ConnectionManager.ConnectToPeer creates a PeerId with outdated BitField
See original GitHub issueHello. I initialize TorrentManager with MagnetLink. I wait until TorrentManager.Torrent != null. Connected peers have BitField with single element. After some time bitfields are fixed. IgnoringPicker throws on BitField.Check meahwhile. This bug can be fixed in MetadataMode.SwitchToRegular but I am not sure it is a good way.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
ConnectionManager.ConnectToPeer creates a PeerId with ...
Connected peers have BitField with single element. ... ConnectionManager.ConnectToPeer creates a PeerId with outdated BitField #196.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

The extra patch is in now! This should be OK to close now.
Let me know if you have any further issues!
Amazing, thanks for checking that so quickly.
I’ll review the usage of the ‘HandshakingPeers’ list as I don’t believe it makes sense to separate these peers from the rest of the ‘ConnectedPeers’. The change went in as part of a large refactor ( https://github.com/mono/monotorrent/commit/b4ee76b33a32698a79bcde8204f4ae328e9da04b ) and there’s no specific reason given for it. I can’t think of any reason why this would be needed.
I’ll merge this change for now so that things are fixed immediately, but i may replace it with an alternative set of changes in the near future!
Thanks!