ntf server: allow retries when creating subscriptions, prohibit subscriptions with the same queue but another notifier key or token #1525
Conversation
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
…riptions with the same queue but another notifier key or token
epoberezkin
commented
Apr 25, 2025
| pure $ | ||
| if notifierKey == registeredNKey | ||
| then NRSubId subId | ||
| then NRSubId ntfSubId |
Member
Author
There was a problem hiding this comment.
this was an old bug that returned empty subscription ID on retry, that would probably trigger failure on SCHK, that would then trigger creating a new notifier credentials and new subscription.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.