Conversation
|
Yeah, I'm just going to piggy back a massive gx update on this. |
License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
fixes #5616 License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
0b2e218 to
e41ac96
Compare
|
Ok, so, I'm getting a really annoying test failure introduced by ipfs/go-bitswap#15. Specifically,
|
This was causing ipfs/kubo#5637 (comment)
|
When in doubt, it's a data-race: libp2p/go-libp2p#464 |
|
(ok, not the only issue...) |
dd0c041 to
4a2e85a
Compare
|
No, that was the issue. I just failed at fixing it. |
License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
4a2e85a to
636bbc7
Compare
(fixes a panic due to a race) License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
| // Enabled by default. | ||
| libp2pOpts = append(libp2pOpts, libp2p.DisableRelay()) | ||
| } else { | ||
| relayOpts := []circuit.RelayOpt{circuit.OptDiscovery} |
There was a problem hiding this comment.
What's the justification for always including circuit.OptDiscovery in relayOpts?
There was a problem hiding this comment.
Without this, p2p circuit addresses that don't explicitly specify the relay won't work. When turning on the relay transport by default in the libp2p constructor, we added this option (the feature was already there) and turned it off by default. However, to maintain functionality (and keep the tests passing) I had to turn it back on in go-ipfs.
mass gx update This commit was moved from ipfs/kubo@0bd181c
Uh oh!
There was an error while loading. Please reload this page.