Change the buffer-aware BUFBE: -> bufbe.#880
Conversation
The buffer-aware work appends a BUFBE: sentinel to the publisher's user_data QoS field. But parse_key_value does not support colons in keys, so all type hashes for buffers using this would be INVALID. Fix this by dropping the colon from the sentinel, which makes it pass parse_key_value and keep type hashes working. Also add in a regression test here. Signed-off-by: Chris Lalancette <clalancette@gmail.com>
|
Here is CI with this and all of the other PRs listed here:
|
fujitatomoya
left a comment
fujitatomoya
left a comment
There was a problem hiding this comment.
the PR description says "no user-facing behavior change" and "should be backported to Lyrical." If anyone has used buffer-aware code based on the unpatched form (are we expecting this fix is going to be merged before release?), this rename is a wire break for them? i guess that is probably not a great idea?
That's a good point, but in my opinion, since Lyrical isn't released yet, this is fine to do. Once Lyrical ships, then I think it would be a breaking change and we'd have to figure something else out. But I'm open to other opinions. |
|
Here's another build with the updates in place:
|
|
@Mergifyio backport lyrical |
✅ Backports have been createdDetails
|
3 participants
Description
The buffer-aware work appends a BUFBE: sentinel to the publisher's user_data QoS field. But parse_key_value does not support colons in keys, so all type hashes for buffers using this would be INVALID.
Fix this by dropping the colon from the sentinel, which makes it pass parse_key_value and keep type hashes working.
Also add in a regression test here.
This should be merged at approximately the same time as #879 , #881 , and ros2/system_tests#592
Is this user-facing behavior change?
No.
Did you use Generative AI?
Yes, Claude Opus 4.7
Additional Information
This should be backported to Lyrical.