Fix of the issue when removal of the last event in the InMemory table… #1844
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.
Purpose
Resolves issue 1822 - Removal of the last stored event in the InMemory table disrupts the references chain, subsequently causing improper behaviour within the InMemory table. Any future inserts are erroneously appended to the removed event, leading to unexpected and undesired outcomes.
Goals
Fix the logic of the remove method in the SnapshotableStreamEventQueue class to gracefully handle the removal of the last item. Reset the
last
variable to point to the previous item if the item being removed is the last one.Security checks