Use unique mangled names when creating Content Filter Topics (backport #762)#769
Merged
Use unique mangled names when creating Content Filter Topics (backport #762)#769
Conversation
Signed-off-by: Mario Dominguez <mariodominguez@eprosima.com> Signed-off-by: Mario-DL <mariodominguez@eprosima.com> (cherry picked from commit 97edce2)
fujitatomoya
approved these changes
Jun 5, 2024
Collaborator
|
CI:
|
ahcorde
approved these changes
Jun 6, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR makes every Content Filter Name unique by adding a static atomic counter. With this change, two or more content-filtered subscriptions can be created for the same topic name.
Tests are included in the following related PRs
This is an automatic backport of pull request Use unique mangled names when creating Content Filter Topics #762 done by Mergify.