- 06 Oct, 2018 1 commit
-
-
vyzo authored
-
- 05 Oct, 2018 1 commit
-
-
vyzo authored
-
- 01 Oct, 2018 1 commit
-
-
vyzo authored
-
- 29 Sep, 2018 1 commit
-
-
Can ZHANG authored
-
- 26 Sep, 2018 3 commits
- 21 Sep, 2018 1 commit
-
-
QYuan authored
-
- 14 Sep, 2018 1 commit
-
-
gukq authored
Signed-off-by: gukq <gukaiqiang@gmail.com>
-
- 13 Sep, 2018 1 commit
-
-
Can ZHANG authored
-
- 10 Sep, 2018 1 commit
-
-
Steven Allen authored
fixes #419 Also call FullClose in a goroutine; no need to block this. (not happy with that but I'm starting to think we need to rethink stream closing, again...)
-
- 08 Sep, 2018 1 commit
-
-
Steven Allen authored
-
- 07 Sep, 2018 1 commit
-
-
Can ZHANG authored
-
- 02 Sep, 2018 1 commit
-
-
Steven Allen authored
(avoids the race condition)
-
- 31 Aug, 2018 1 commit
-
-
Marten Seemann authored
-
- 28 Aug, 2018 1 commit
-
-
Cole Brown authored
-
- 13 Aug, 2018 1 commit
-
-
Steven Allen authored
This reverts commit aca83b9b, reversing changes made to 86b8929d. This was is not the correct fix. We already expose these addresses via the host's AllAddrs method. The real problem is probably that we just don't ever tell anyone about them (unless we disconnect and reconnect to our nearby DHT nodes). We need an address gossip protocol.
-
- 09 Aug, 2018 1 commit
-
-
Steven Allen authored
and regenerate protobuf files
-
- 08 Aug, 2018 3 commits
-
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
- 02 Aug, 2018 1 commit
-
-
Steven Allen authored
related to #383 I won't call this *fixed* yet but it should help.
-
- 27 Jul, 2018 1 commit
-
-
Steven Allen authored
Currently, we leak a stream. We could use FullClose but, IMO, it's not worth it. We might as well just reset and walk away.
-
- 15 Jun, 2018 1 commit
-
-
Steven Allen authored
This happens all the time in tests where we intentionally use fake keys for performance. Anyways, users probably don't want their logs spammed with errors they can't do anything about.
-
- 12 Jun, 2018 1 commit
-
-
Łukasz Kurowski authored
-
- 09 Jun, 2018 1 commit
-
-
Steven Allen authored
(counting open connections requires copying)
-
- 06 Jun, 2018 2 commits
-
-
Erin Swenson-Healey authored
-
Erin Swenson-Healey authored
-
- 05 Jun, 2018 1 commit
-
-
Steven Allen authored
Also, make the libp2p constructor fully useful. There should now be no need to manually construct a swarm/host.
-
- 27 Mar, 2018 1 commit
-
-
Jakub Sztandera authored
It is source of most warning noise in Warning channel and we would like to enable warning channel some time in future by default
-
- 16 Feb, 2018 1 commit
-
-
Hector Sanjuan authored
License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
-
- 14 Feb, 2018 1 commit
-
-
Łukasz Magiera authored
-
- 28 Jan, 2018 1 commit
-
-
Steven Allen authored
-
- 27 Jan, 2018 1 commit
-
-
Alexey Kholupko authored
Closes #256
-
- 20 Jan, 2018 3 commits
-
-
Steven Allen authored
-
Steven Allen authored
This way, we actually process disconnect notifications (and reduce the lifetime on peer addr records).
-
Steven Allen authored
This commit prevents us from repeatedly extending the lifetimes of all observed addresses if a peer keeps on reconnecting. It also fixes two race conditions: 1. We may end up processing a disconnect after a re-connect and may accidentally give the addresses associated with that peer a RecentlyConnectedAddrTTL instead of a ConnectedAddrTTL. 2. We may end up processing a connect after the associated disconnect storing the associated peer addresses indefinitely.
-
- 17 Nov, 2017 2 commits
-
-
Steven Allen authored
There's really no reason to *only* do this if we have relays enabled. Doing it this way makes `go vet` happier and reduces conditional logic.
-
Kevin Atkinson authored
-
- 06 Oct, 2017 1 commit
-
-
Jeromy authored
-