Updating RTCM receiver pubsub to use IOM receiver tags #368
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.
Requires the following PRs:
Fixes issue in a comment described in #364, which is a result of DUNE-DAQ/iomanager#70.
In short: Only one subscriber was allowed in pubsub connection. When trying to run with two
RandomTCMaker
s, both usingkTimeSync
, they would both try to connect response/callback function to the sameTimeSync
connection pubsub, resulting in a crash.The PRs above add new feature in
IOManager
to allow multiple receivers for a connection, and this PR makesRandomTCMaker
s using this new feature.Tested by running two
RandomTCMakers
withkTimeSync
, and checkout the log messages / output HDF5 file.Might need few other packages (e.g.
appfwk
) for others to test.