- 08 Nov, 2018 1 commit
-
-
Steven Allen authored
This was probably failing (rarely) due to the fact that we're shrinking the timeout asynchronously (I think?).
-
- 07 Nov, 2018 1 commit
-
-
Steven Allen authored
RandLocalTCPAddress is mostly useful when we *actually* want to listen on a real address. Unfortunately, when running a bunch of tests, we can actually run out. With this change, a collision means we have a duplicate peer ID so yeah... fixes #473
-
- 06 Nov, 2018 1 commit
-
-
vyzo authored
-
- 04 Nov, 2018 30 commits
-
-
vyzo authored
-
vyzo authored
-
vyzo authored
also check that we don't initially advertise any.
-
vyzo authored
macosx seems to fail intermittently, and that race is the likely culprit.
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
vyzo authored
-
- 24 Oct, 2018 4 commits
-
-
Steven Allen authored
-
Steven Allen authored
This was causing https://github.com/ipfs/go-ipfs/pull/5637#issuecomment-432792969
-
Steven Allen authored
-
Steven Allen authored
Sending a protocol version is nice. However, this "disconnect if our versions are different" logic makes the version entirely useless (because we can't change it). Really, each indevidual protocol is versioned so let's just leave it at that. If we make a breaking change that requires a protocol bump, we can do that and then switch on the other side's version. However, we'll have to wait for the entire network to upgrade for that to work.
-
- 19 Oct, 2018 3 commits