[FIXED] LeafNode: Don't forward shadow sub unsubscribe if spoke leafnode #7259
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 is related to PR #5519 where the propagation of a shadow subscription was suppressed for a subscription coming from a spoke leafnode connection, but the handling of the unsubscribe of such shadow subscription was not fixed, which could result in removing a legitimate interest.
The test
TestLeafNodeDupeDeliveryQueueSubAndPlainSub
that was added in PR #5519 was modified to demonstrate what would have been the issue without the fix in this PR.Signed-off-by: Ivan Kozlovic ivan@synadia.com