- 15 Jan, 2015 4 commits
-
-
Jeromy authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Juan Batiz-Benet authored
Good thing, i checked one wrong, too!
-
- 14 Jan, 2015 2 commits
-
-
Juan Batiz-Benet authored
the travis docs say the env flag TRAVIS=true but, i want to make absolutely sure. explicitness leaves less room for error.
-
Juan Batiz-Benet authored
-
- 13 Jan, 2015 21 commits
-
-
Juan Batiz-Benet authored
p2p/net/swarm: more connection bugs
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
this is actually pretty important in case some peers end up changing addrs, so others dont fail dialing simply for picking the wrong addr to start with.
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
This commit introduces a backoff when failing to dial peers. It makes everything much faster.
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
* filtering InterfaceListenAddresses(s) instead * return error if for loops skip * large dial timeout
-
Brian Tiger Chow authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
This adds two checks after a successful conn.Dial * if the remote peer is not who we wanted, close conn * if the remove peer is outselves, close conn (the second is redundant, but the codebase may evolve to end up disabling the first check, so keeping the second in place helps) note: Loopback addresses are actually sent out (they _have to be_, in cases where there are >1 node in the same machine), so many times when trying connections, nodes end up dialing themselves.
-
Juan Batiz-Benet authored
-
- 12 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
cc @whyrusleeping
-
- 11 Jan, 2015 4 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
Instead of erroring out, which would break the listener, we instead log a message and continue. This is not an error, the internet is a place with lots of probing + connection failures.
-
Juan Batiz-Benet authored
This should handle early breakages, where a failing connection would take out the listener entirely. There are probably other errors we should be handling here, like secure connection failures.
-
Juan Batiz-Benet authored
-
- 10 Jan, 2015 1 commit
-
-
Brian Tiger Chow authored
BenchmarkSign1B 1000 2406924 ns/op BenchmarkSign10B 1000 2360527 ns/op BenchmarkSign100B 1000 2354136 ns/op BenchmarkSign1000B 500 2361775 ns/op BenchmarkSign10000B 500 2415993 ns/op BenchmarkSign100000B 500 2718051 ns/op BenchmarkVerify1B 30000 52117 ns/op BenchmarkVerify10B 30000 50968 ns/op BenchmarkVerify100B 30000 51037 ns/op BenchmarkVerify1000B 30000 56768 ns/op BenchmarkVerify10000B 10000 105744 ns/op BenchmarkVerify100000B 2000 628530 ns/op
-
- 09 Jan, 2015 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 08 Jan, 2015 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 05 Jan, 2015 3 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-