fix first pub message not always arriving#54
Merged
Conversation
added 5 commits
May 3, 2026 23:19
use socket monitor (and test pub) to ensure pub is ready in Ready
bugfix; should check err is not null before setting it in error case
change compression check from just heuristically checking that messages start with '(' to more robust 4-byte check
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
2 participants
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.
use socket monitor (and test pub) to ensure pub is ready in Ready
also:
set ZMQ_IMMEDIATE on pub socket, apparently it's relevant
small bugfix; should check err is not null before setting it in error case
change compression check from just heuristically checking that messages start with '(' to more robust 4-byte check