memstore: refresh stale Last values and hold write lock in MultiLastSeqs#7865
Merged
neilalexander merged 1 commit intomainfrom Feb 24, 2026
Merged
memstore: refresh stale Last values and hold write lock in MultiLastSeqs#7865neilalexander merged 1 commit intomainfrom
neilalexander merged 1 commit intomainfrom
Conversation
Member
MauriceVanVeen
left a comment
MauriceVanVeen
left a comment
There was a problem hiding this comment.
LGTM, but could you add a test for this?
Signed-off-by: Daniele Sciascia <daniele@nats.io>
sciascid
force-pushed
the
memstore-fix-stale-last-usage
branch
from
3dbde43 to
a641b4e
Compare
neilalexander
added a commit
that referenced
this pull request
Feb 25, 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
3 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.
Avoid access to potentially stale
ss.Lastin MultiLastSeqs.Signed-off-by: Daniele Sciascia daniele@nats.io