statement-store: Stop panicking on affinity updates when the statement protocol is disabled - #3334
Merged
Merged
Conversation
7 tasks
AndreiEres
changed the title
michalkucharczyk
approved these changes
Aug 7, 2026
Co-authored-by: Michal Kucharczyk <1728078+michalkucharczyk@users.noreply.github.com>
AndreiEres
enabled auto-merge (squash)
August 7, 2026 14:39
lexnv
approved these changes
Aug 7, 2026
dmitry-markin
approved these changes
Aug 10, 2026
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
4 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.
Calling
statement_subscribeStatementon a chain that runs without the statement protocol panics: inserting the subscription schedules a topic-affinity update, and the schedulerexpects the protocol config to be present. The scheduler now returns early instead — subscriptions can still be created in that case, and there is no affinity to advertise.