- 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
-
- 24 Sep, 2017 1 commit
-
-
Eric Harris-Braun authored
-
- 21 Sep, 2017 1 commit
-
-
vyzo authored
-
- 14 Sep, 2017 1 commit
-
-
Steven Allen authored
Before, on close, we: 1. Weren't completing the write. 2. Flushing the buffer without waiting the latency delay. This fixes that by using two separate channels for close/reset and ignoring the close channel in deliverOrWait.
-
- 13 Sep, 2017 5 commits
-
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
* Fix the tests to work with separate reset/close methods. * Ensure we interrupt writes on reset. * Always delay the proper time even if we're sending short messages. * Copy buffers as we send them. `Write` is not allowed to hang onto buffers. If we run into performance issues, we can always add a buffer pool.
-
- 07 Aug, 2017 2 commits
-
-
Lars Gierth authored
-
Lars Gierth authored
-
- 04 Aug, 2017 1 commit
-
-
Gurinder Singh authored
-
- 02 Aug, 2017 2 commits
- 01 Aug, 2017 2 commits
- 27 Jul, 2017 1 commit
-
-
Steven Allen authored
-
- 22 Jul, 2017 1 commit
-
-
vyzo authored
-
- 21 Jul, 2017 1 commit
-
-
vyzo authored
-
- 12 Jul, 2017 1 commit
-
-
Jeromy authored
-
- 11 Jul, 2017 1 commit
-
-
Jeromy authored
-
- 05 Jun, 2017 1 commit
-
-
Enzo Haussecker authored
-
- 03 Jun, 2017 1 commit
-
-
Enzo Haussecker authored
-
- 31 May, 2017 1 commit
-
-
Lars Gierth authored
There were previously 4 different ways of passing various options into BasicHost construction. 1. Function parameters to New 2. Option parameters to New 3. Global variables, e.g. NegotiateTimeout 4. Options struct, in the calling code in go-ipfs This changeset deprecated all of these, and introduces the HostOpts struct to replace them. It also introduces a new constructor called NewHost, which accepts a *HostOpts. The old New constructor continues to work the same way, but is from now on deprecated too.
-