Messages are not propagated when only some nodes subscribe a topic about js-libp2p-gossipsub HOT 8 CLOSED

I'm curious how this scenario works using go-libp2p.

It seems C won't send the message to B because nodes only send messages to peers which have subscribed to the topic (or direct peers).

As far as I know, publishing a message follows something like this:

• publish to all direct peers
• if flood-publishing is enabled
  • publish to all peers subscribed to the topic
• else
  • publish to floodsub peers subscribed to the topic
  • if we are in the mesh for the topic
    • publish to mesh peers (peers subscribed to the topic)
  • else
    • publish to fanout peers (possibly creating fanout peers from peers subscribed to the topic)

from js-libp2p-gossipsub.

@wemeetagain I also noticed that, both in go code and spec. This is strange though, while I understand that the real world scenarios are bigger topologies, I would expect this to work. What do you think?

I did a small test with go daemon and it has the same behaviour and the other peer does not receive messages https://github.com/libp2p/interop/blob/chore/try-3-go-gossipsub-with-hop/test/pubsub/gossipsub/go2go2go.js

from js-libp2p-gossipsub.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

from js-libp2p-gossipsub.

This issue or pull request has been automatically been closed due to inactivity.

from js-libp2p-gossipsub.

is this still an issue?

from js-libp2p-gossipsub.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

from js-libp2p-gossipsub.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

from js-libp2p-gossipsub.

Please re-open if current version still causes this issue. The publish logic has been modified

from js-libp2p-gossipsub.