Closed philiprodrigues closed 2 years ago
It looks like there's an issue with the conn_refs, both have the same name, so I think they are hiding each other.
This will have to be a new feature, since neither iomanager
or networkmanager
support subscribing to topics that are on different connections in a single subscriber. (I believe that the underlying ipm
and ZMQ
implementations would support this behavior, though)
I believe this Issue will be made obsolete by https://github.com/DUNE-DAQ/daqconf/pull/116
I also believe that this Issue has become obsolete with changes in daqconf, so I'm closing it.
(I'm filing this in
iomanager
because the same issue wasn't seen in 2.11.x, but it's possible the actual problem is indaqconf
)In the recent VD coldbox runs, we saw that
TPWriter
only writes TPs from one of the input links. This occurs with v3.0.0 but not with v2.11.1.This can be reproduced in a test setup with, eg, this
daqconf
command:Then the
tpwriter_init.json
file contains all of the relevant connections andconn_refs
:but only the last item in the
conn_refs
is actually subscribed to. From the TPWriter log:but no corresponding log message for
tpsets_ru0_link0_sub
. If I swap the order of the two dictionaries inconn_refs
in the json file, the log shows thattpsets_ru0_link0_sub
is subscribed to.