Closed samcarey closed 10 months ago
Yes, that was a good catch!
The processing path for DATA retransmits always inserted the current (retransmit) time as source timestamp, instead of the timestamp specified by the application. There was even a todo-marker indicating a missing bit of implementation in the code.
Please check out the latest master
version and see it fixes the problem for you.
Is it ok to you to include your test case into RustDDS unit tests?
Fixed in version 0.8.6.
I am trying to read the original source timestamp of a sample written from from a different participant than the reader. Unfortunately, this only seems to work if both reader and writer are created from the same participant.
Failing test:
Result:
As you can see, the resulting "source_timestamp" is reported to be just over 3 seconds after the original, which is the amount of time we slept between writing and reading (and it always nearly matches for different durations). This suggests that the source_timestamp is actually being set at the time of reading instead of writing.
If you replace
with
in the above test, such that both reader and writer are from the same domain participant, it will pass.
Is this a bug?