Skip to content

Fix issue where ksn might be ignored (#1067) #1069

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
merged 2 commits into from
Dec 18, 2023

Conversation

MeirShpilraien
Copy link
Collaborator

@MeirShpilraien MeirShpilraien commented Dec 18, 2023

The issue is that the detached_ctx_guard was released before the _notification_blocker. This cause the Redis lock to be released before the notification was resumed. If a notification would have arrive in between the time the Redis lock was released to the time the notifications was resumed, we would have lost it.

(cherry picked from commit e5c9a5e)

@MeirShpilraien MeirShpilraien merged commit 7946531 into 2.0 Dec 18, 2023
@MeirShpilraien MeirShpilraien deleted the fix_issue_where_ksn_might_be_ignored_2.0 branch December 18, 2023 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants