Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Only one Subscriber can listen on a connection in an app #70

Open
eflumerf opened this issue Nov 8, 2023 · 0 comments · May be fixed by #79
Open

Only one Subscriber can listen on a connection in an app #70

eflumerf opened this issue Nov 8, 2023 · 0 comments · May be fixed by #79
Labels
bug Something isn't working

Comments

@eflumerf
Copy link
Member

eflumerf commented Nov 8, 2023

While testing the updated listrev code, I had a situation where 2 instances of the same DAQModule were in an app, and they both tried to register callbacks on a single PubSub connection. Since NetworkReceiverModel only supports a single callback per connection, only one of the DAQModules actually received the data coming over this connection, which caused the test to fail.

We should look into how to handle this case, so that "gg" listrev_test configurations are possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a "tag" parameter to ConnectionId that can be used to differentiate DUNE-DAQ/iomanager
1 participant
@eflumerf