[FIXED] Parallel stream restore panic#7503
Merged
neilalexander merged 1 commit intomainfrom Nov 3, 2025
Merged
Conversation
6d0ac9e to
65cc432
Compare
Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
65cc432 to
c85269f
Compare
This was referenced Nov 5, 2025
neilalexander
added a commit
that referenced
this pull request
Nov 5, 2025
neilalexander
added a commit
that referenced
this pull request
Nov 5, 2025
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
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.
Due to the stream restore parallelization introduced in #7482, we can panic on
access time service not running. Sinceats.Register()can now be called in parallel as well.We can simply store an initial value, on startup it's no issue that this timestamp is only slightly stale.
Signed-off-by: Maurice van Veen github@mauricevanveen.com