46b5513add
gomod: update go-libp2p-circuit
2019-08-02 21:12:51 +03:00
4a8d3557c0
upgrade peerstore.
2019-07-10 15:54:09 +01:00
58fa778c37
dep: update go-libp2p-swarm to be less noisy
...
The noisy tests are getting annoying.
2019-07-04 12:55:10 -07:00
e69d17141c
integrate the event bus, handle protocol update events, make identify emit deltas ( #659 )
2019-06-24 14:44:47 +01:00
0635f49abb
fix: update to non-coalescing yamux
2019-05-31 20:36:29 -07:00
d87f89314c
Consolidate abstractions and core types into go-libp2p-core ( #601 )
2019-05-26 22:55:46 +01:00
6813fdd0d1
gomod: update go-ws-transport
2019-05-24 15:09:25 +03:00
29d536740b
gomod: update go-libp2p-circuit
2019-05-24 13:51:22 +03:00
d3fad322ee
gomod: update go-libp2p-discovery
2019-05-24 12:40:38 +03:00
6f25e76e56
gomod: update go-libp2p-circuit@v0.0.8
2019-05-22 20:55:20 +03:00
58ac4c8110
gomod: update go-ws-transport
2019-05-22 11:57:05 +03:00
cad2c649ac
gomod: update go-libp2p-autonat
2019-05-22 11:54:32 +03:00
26f880b899
dep: import go-smux-* into the libp2p org
...
0. I imported whyrusleeping/go-smux-* into go mod.
1. To handle post-1.0 tags, I renamed all of our "gx" tags to "gx/v..." as we
did with the rest of libp2p.
2. This broke _everything_ because `go mod` absolutely can't deal with deleted
tags if any transitive go.sum file mentions the tag.
3. To fix this, I first got rid of all mentions of these 2.x+incompatible tags.
4. Unfortunately, I realized this was still going to be a nightmare for
downstream users as a `go get github.com/libp2p/go-libp2p@latest` on a fresh
clone (no go mod cache) would fail. I didn't want to have to explain to all
of our downstream users "please delete your go.sum files!".
5. So I did what I should have done in the first place:
a. I restored those tags.
b. I forked all the whyrusleeping/go-smux-* repositories (and
whyrusleeping/yamux) into the libp2p org where.
c. I removed all tags but the _new_ go-mod tags on those new libp2p repos.
What does this mean for downstream users? If they manually import any of these
stream muxer repos, they'll have to fix their imports. Otherwise, it shouldn't
make a difference.
2019-05-21 19:44:12 -07:00
dea021f127
dep: update go-smux-*
...
And friends. Emergency release to handle some tags I deleted.
2019-05-21 16:51:55 -07:00
946aa0e70d
gomod: update go-mplex@v0.0.3
2019-05-22 00:20:09 +03:00
661843a33b
gomod: update go-libp2p-interface-connmgr
2019-05-21 14:02:37 +03:00
f3ed4cf7e8
gomod: update go-libp2p-peerstore@v0.0.6
2019-05-18 12:07:18 +03:00
fc6f373465
gomod: update go-libp2p-discovery
2019-05-17 22:04:29 +03:00
fb404b5c2a
gomod: update go-mplex
2019-05-11 13:41:27 +03:00
708d17c2d0
dep: update goprocess
...
fixes a panic and has a few more perf improvements
2019-05-09 15:18:35 -07:00
e8e29ddabc
dep: update multihash, multiaddr, and peer
...
Also updates our base58 library.
2019-05-08 14:38:23 -07:00
d8fed21c5d
gomod: update go-multistream
2019-05-08 20:11:05 +03:00
1b9cf3e2cb
test: disable flaky autorelay test in CI
...
This keeps breaking travis.
2019-05-07 15:53:37 -07:00
643b9acbb7
Merge pull request #625 from libp2p/dep/update-goprocess
...
dep: update goprocess
2019-05-07 15:17:26 -07:00
26fe9dc6c9
dep: update goprocess
...
1. It now supports go modules.
2. It should spawn fewer goroutines, especially when used with contexts.
2019-05-07 15:09:13 -07:00
b5b6230ded
gomod: update go-libp2p-circuit
2019-05-07 22:39:38 +03:00
a1bae0a3ef
gomod: update go-libp2p-host, go-libp2p-interface-connmgr
2019-05-06 15:16:00 +03:00
afd88c4dce
gomod: update go-libp2p-crypto
2019-05-03 22:30:20 +03:00
b481650dbc
gomod: update go-libp2p-circuit
2019-05-02 19:34:42 +03:00
273a5f2a9d
update go-multistream
2019-04-30 19:04:50 +03:00
621aa0da19
dep: update peerstore and secio
...
Pull in a panic fix and a fix for https://github.com/libp2p/go-mplex/issues/43
2019-04-28 12:44:50 -07:00
8e2547048f
gomod: update go-libp2p-peerstore
2019-04-28 10:38:49 +03:00
eeac0bb952
update upgraders to maybe fix a concurrent connection write issue
2019-04-26 01:40:19 -07:00
5f198db75d
gomod: update go-libp2p-swarm, go-libp2p-peerstore
2019-04-25 20:11:36 +03:00
330481f135
dep: update secio
2019-04-22 09:46:24 -07:00
8d2457577d
gomod: update go-libp2p-discovery
2019-04-16 10:45:57 +03:00
e2acda1c42
gomod: update go-libp2p-peerstore
2019-04-12 20:59:41 +03:00
ef92f67df6
dep: update go-libp2p-nat again
...
This time, don't try to map the same internal/external port. Random ports are
safer as not all NAT devices can handle port conflicts...
2019-04-12 10:29:02 -07:00
b94e2ce8f3
gomod: update go-libp2p-circuit
2019-04-12 10:52:17 +03:00
2c33dc34ac
dep: update go-libp2p-nat
...
Switches to libp2p/go-nat which has some improved gateway detection logic.
2019-04-11 22:13:02 -07:00
25adea6d56
gomod: update go-libp2p-net, go-libp2p-swarm, and go-libp2p-circuit
2019-04-10 23:09:17 +03:00
2bd14ad185
update go-libp2p-autonat
2019-04-10 10:42:16 +03:00
9bb06fcb2a
gomod: update go-libp2p-circuit
2019-04-08 19:07:47 +03:00
2a8398b05f
dep: update transports
2019-04-04 00:47:38 -07:00
b33e731689
gomod: update go-libp2p-autonat
2019-04-04 10:19:25 +03:00
eb20b61a6d
update go-smux-yamux
2019-03-07 13:43:17 +02:00
3617750071
better nat mapping
...
1. Update to work with https://github.com/libp2p/go-libp2p-nat/pull/14 .
2. Avoid observed addrs when our NAT tells us about external addrs.
3. Ignore bad addrs reported by our NAT. Substitute with observed addrs.
4. Fix https://github.com/libp2p/go-libp2p/issues/428 .
2019-03-06 10:56:49 -08:00
d0ce3e1bac
dep: update autonat
2019-03-06 10:54:27 -08:00
c4b498537c
add gomod support // tag v0.0.1.
2019-03-02 00:13:40 +00:00
vyzo
Raúl Kripalani
Steven Allen