We have the following scenario:
We have created a c++ application using the fast-dds library.
We also have a python application (mainly using subscribers) for data extraction.
For consistency and keeping track of participants, publishers and subscribers we have added
a DomainListener in the c++ application.
Using fast-dds v2.14.2 -> v2.14.2
fast-cdr v2.2.3 -> v2.2.3
And fast-dds-python v1.4.3 -> v1.4.3
Everything is working as expected.
-> Every single participant, publisher and subscriber are also detected when created/dropped in the domainlistener methods
on_participant_discovery
on_data_writer_discovery
on_data_reader_discovery
Updating the fast-dds to v3.2.2 ->v3.2.2
fast-cdr v2.3.0 -> v2.3.0
(note: we also tried with an older version of fast-cdr v2.2.3 -> v2.2.3 )
And using the fast-dds-python v2.2.0 -> v2.2.0
The python application starts, but the c++ application detects only the created participants.
-
The publisher and subscribers are not longer detected (when created and/or dropped) in the domain listener via
on_data_writer_discovery
on_data_reader_discovery
-
Python subscribers stop receiving data from the c++ application. Also the python function
def on_publication_matched(self, datawriter, info) :
stopped being called, thus it fails to connect(?! or match) the publisher and subscribers.
The python application was created as described in the example - https://fast-dds.docs.eprosima.com/en/v3.2.2/fastdds/getting_started/simple_python_app/simple_python_app.html
We have the following scenario:
We have created a c++ application using the fast-dds library.
We also have a python application (mainly using subscribers) for data extraction.
For consistency and keeping track of participants, publishers and subscribers we have added
a DomainListener in the c++ application.
Using fast-dds v2.14.2 -> v2.14.2
fast-cdr v2.2.3 -> v2.2.3
And fast-dds-python v1.4.3 -> v1.4.3
Everything is working as expected.
-> Every single participant, publisher and subscriber are also detected when created/dropped in the domainlistener methods
on_participant_discovery
on_data_writer_discovery
on_data_reader_discovery
Updating the fast-dds to v3.2.2 ->v3.2.2
fast-cdr v2.3.0 -> v2.3.0
(note: we also tried with an older version of fast-cdr v2.2.3 -> v2.2.3 )
And using the fast-dds-python v2.2.0 -> v2.2.0
The python application starts, but the c++ application detects only the created participants.
The publisher and subscribers are not longer detected (when created and/or dropped) in the domain listener via
on_data_writer_discovery
on_data_reader_discovery
Python subscribers stop receiving data from the c++ application. Also the python function
def on_publication_matched(self, datawriter, info) :
stopped being called, thus it fails to connect(?! or match) the publisher and subscribers.
The python application was created as described in the example - https://fast-dds.docs.eprosima.com/en/v3.2.2/fastdds/getting_started/simple_python_app/simple_python_app.html