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
If we are using GossipSub to publish a message for a topic, the API doesn't return any error/failure in case there are no peers available for that topic.
If there are no fan-out peers identified/discovered for that topic, shouldn't an error be returned to the caller indicating that not enough peers are available to publish the message?
Especially since a node is not required to subscribe to a topic to which it wants to publish messages, I am thinking this would be a good to have.
The text was updated successfully, but these errors were encountered:
Ok, but shouldn't it be the default option.
I am wondering as to why would a node want to publish if there are no peers to publish. Is there some use-case i am missing?
If we are using GossipSub to publish a message for a topic, the API doesn't return any error/failure in case there are no peers available for that topic.
If there are no fan-out peers identified/discovered for that topic, shouldn't an error be returned to the caller indicating that not enough peers are available to publish the message?
Especially since a node is not required to subscribe to a topic to which it wants to publish messages, I am thinking this would be a good to have.
The text was updated successfully, but these errors were encountered: