You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like pubsub w/ gossipsub router yields messages we publish on the local peer to the local peer. This seems to be because we are using the same infrastructure to publish data as we are to read incoming data.
In particular, review use of self.subscribed_topics_receive[topic_id]. It seems like this is the only way right now to get gossip messages from others, but given the call to notify subscriptions in push_msg, we end up getting a reference to the message back locally.
The text was updated successfully, but these errors were encountered:
It looks like pubsub w/ gossipsub router yields messages we publish on the local peer to the local peer. This seems to be because we are using the same infrastructure to publish data as we are to read incoming data.
In particular, review use of
self.subscribed_topics_receive[topic_id]
. It seems like this is the only way right now to get gossip messages from others, but given the call to notify subscriptions inpush_msg
, we end up getting a reference to the message back locally.The text was updated successfully, but these errors were encountered: