06a12f17b7
reduce log verbosity; debug mostly
2020-09-01 20:42:50 +03:00
ae55bf9603
upgrade deps + interoperable uvarint delimited writer/reader.
2020-07-30 14:00:54 +03:00
e18b4edd9a
drop warning about failure to open stream to a debug log
2020-06-12 23:47:16 +03:00
ce9a0b7edf
use log.Warn instead of Warning
2020-05-05 21:10:14 +03:00
0d884f3e90
Topic relay discovery
...
Incorporated relays to
exiting discovery logic
and added them to topic
before-remove guard.
2020-05-01 12:22:22 +03:00
1f147c2457
make wire protocol message size configurable. ( #261 )
2020-02-25 18:07:16 -08:00
5ef7439d71
interface: New Topic + TopicEventHandlers objects.
...
Added PubSub.Join(topic) that returns a Topic object. This object can be Subscribed and Published to as well as to get a TopicEventHandler for topic events. This means that the Subscription object will no longer handle PeerEvents and that PubSub's Publish and Subscribe functions are deprecated.
2019-10-31 15:37:44 -04:00
49274b0e8a
migrate to consolidated types. ( #185 )
2019-05-26 17:19:03 +01:00
6d2f8e649c
discriminate stream errors from unsupported protocols
2018-12-14 00:33:30 +02:00
fc7795c38f
simplify peer disconnect detection logic to ensure a single outgoing stream
2018-12-13 22:52:59 +02:00
2621f893e6
rework peer tracking logic to handle multiple connections
2018-12-13 19:53:12 +02:00
bd1a4630b9
move to go-libp2p-pubsub
...
Updates for move from go-floodsub to go-libp2p-pubsub.
fixes https://github.com/libp2p/go-libp2p-pubsub/issues/4
2018-10-18 21:10:16 +01:00
71d32b2f3d
fix missing reset on write errors
2018-10-12 12:22:26 +03:00
0827f5e955
gx publish 0.9.31
2018-10-04 19:23:53 -04:00
1abb0209ce
gx publish 0.9.30
2018-10-04 18:41:48 -04:00
a3003697f6
more idiomatic copyRPC
2018-08-28 21:35:00 +03:00
73b338aa6d
fix nil pointer dereference in copyRPC
2018-08-28 21:17:00 +03:00
de4adefafb
fix data race in ownership of RPC when piggybacking control messages.
2018-08-28 21:07:18 +03:00
6a177a7396
handle gossipsub control messages
2018-06-12 08:00:17 -07:00
f6afd637b8
make sure to *fully* close streams
...
We need to wait for the EOF from the other side when closing from the sending
side (unless we've already seen an EOF).
2018-06-05 15:53:25 -07:00
098f1d5819
demote errors/warnings to info
...
* dropped/killed connections are not errors.
* handleIncomingRPC/publishMessage do not return errors.
2018-01-26 15:00:47 -08:00
56ea7752e8
better worker cleanup
...
1. Don't hang marking a peer as dead if we're shutting down.
2. No need to "drain" the outgoing channel anymore. This may have been necessary
to prevent a deadlock where the main loop blocked on sending on sending a
message while we waited to tell the main loop that the peer was dead. However,
this is no longer an issue (we never block on sending).
2017-10-14 11:19:21 -07:00
3e0c53e2a7
mark the peer as dead if the inbound stream closes
...
fixes #38
2017-10-14 09:24:44 -07:00
238bd82a7f
use reset where appropriate
...
(especially when walking away from read-only streams)
2017-09-15 16:28:46 -07:00
90657d5d53
update dependencies
2016-10-05 12:47:20 -07:00
a16546a7ee
move code to libp2p repo
2016-09-12 20:10:48 -07:00
dd331f38c6
more code cleanup, remove debug statements, add support for multiple
...
messages and topics
2016-09-12 13:22:16 -07:00
ab2fef7c1b
refactor publish messaging
2016-09-11 13:56:07 -07:00
vyzo
Raúl Kripalani
Jeromy
Lukasz Zimnoch
Adin Schmahmann
Steven Allen
Kevin Atkinson
Jeromy