-
Notifications
You must be signed in to change notification settings - Fork 110
Type hash distribution in discovery (rep2011) #437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
clalancette
merged 15 commits into
ros2:rolling
from
emersonknapp:emersonknapp/type-version-hash
Mar 26, 2023
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
edc3465
WIP type_version_hash just fix compile for API change
emersonknapp 7895b0c
Starting to transfer type hash values, but need to interleave keyval …
emersonknapp 70cffca
WIP user-data type hash passing
emersonknapp ce2a99c
Fetching request and response type hashes
emersonknapp 216fcd9
First pass type hash struct
emersonknapp ec2f14a
use common encoder fn
emersonknapp 1c645d6
Log type hash in discovery
emersonknapp 46c8e21
Fix incorrect qos usage
emersonknapp 773d192
Fix linter
emersonknapp 90ff03e
Use new fn signature
emersonknapp d9581c0
Address review comments
emersonknapp b14c4dd
Minor reformatting
emersonknapp f799d89
Add warning on type hash codec failure
emersonknapp 0d823ec
Use new typesupport hashes
emersonknapp 10938d6
Free the user data
emersonknapp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure we are leaking the
userdatahere. At least, the implementation in https://github.com/eclipse-cyclonedds/cyclonedds/blob/11b923aceb2faa506459fee6cfd708345569ac43/src/core/ddsc/src/dds_qos.c#L31 (which is whatdds_qget_userdatacalls) seems to allocate memory, and we don't seem to be freeing it anywhere.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! Rebased (all 4 prs) and added
RCPPUTILS_SCOPE_EXIT(dds_free(userdata));in the if block.