You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to your documentation, there is a compatibility rule for the latency budget QoS policy. The DataWriter duration must be lower or equal to the DataReader duration.
So, based on the reasons described above, I expected that if I created the DataWriter and DataReader with the QoS described below, the listener would trigger an alert
Is there an already existing issue for this?
Expected behavior
According to your documentation, there is a compatibility rule for the latency budget QoS policy.
The DataWriter duration must be lower or equal to the DataReader duration.
So, based on the reasons described above, I expected that if I created the DataWriter and DataReader with the QoS described below, the listener would trigger an alert
Current behavior
However, when I run the code, there is no alert.
Steps to reproduce
Here is the sample main.cpp file.
Here are my PoC project.
fast_dds_latency_budget.zip
Fast DDS version/commit
I checked it with FastDDS v2.11.1, but I think this is still not worked with latest commit (e53a72a)
Platform/Architecture
Ubuntu Focal 20.04 amd64
Transport layer
Default configuration, UDPv4 & SHM, Intra-process
Additional context
No response
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response
The text was updated successfully, but these errors were encountered: