fix: publish/getMessages ignore config.waku.pubSubTopic (hardcoded to old cluster) - #93
Open
munikes wants to merge 1 commit into
Open
fix: publish/getMessages ignore config.waku.pubSubTopic (hardcoded to old cluster)#93munikes wants to merge 1 commit into
munikes wants to merge 1 commit into
Conversation
… dead cluster 0 topic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WakuRequestMethods.PublishMessage/GetMessages hardcode the relay path to /waku/2/rs/0/1 regardless of config.waku.pubSubTopic. Any deployment that changes the pubsub topic (e.g. after a cluster migration) silently keeps publishing/reading on the old topic — no error, the broadcaster looks healthy but nobody ever sees its fee announcements. Fixed by building the relay path from the actual topic passed into publish()/getMessages().