Skip to content

[FIXED] DeleteRange deletes one message too much#6111

Merged
derekcollison merged 1 commit intomainfrom
maurice/delete-range-deletes-too-much
Nov 12, 2024
Merged

[FIXED] DeleteRange deletes one message too much#6111
derekcollison merged 1 commit intomainfrom
maurice/delete-range-deletes-too-much

Conversation

@MauriceVanVeen
Copy link
Copy Markdown
Member

When a DeleteRange was used to mark deletes, when looping over it with dr.Range(..) it would delete one message too much.

Compared with a DeleteSlice the DeleteRange also didn't return the correct last for dr.State(). Also being +1 what it should be.

Signed-off-by: Maurice van Veen github@mauricevanveen.com

Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
@MauriceVanVeen MauriceVanVeen requested a review from a team as a code owner November 12, 2024 10:19
Copy link
Copy Markdown
Member

@neilalexander neilalexander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekcollison derekcollison merged commit dd0c986 into main Nov 12, 2024
@derekcollison derekcollison deleted the maurice/delete-range-deletes-too-much branch November 12, 2024 16:21
neilalexander added a commit that referenced this pull request Nov 12, 2024
Includes the following:

* Some tweaks to the NRG test helpers
* #6055
* #6061
* #6065 
* #6041 (but with `math/rand`
instead of `math/rand/v2` due to an older Go version in CI for 2.10.x)
* #6066
* #6067
* #6069
* #6075
* #6082
* #6087
* #6086
* #6088
* #6089
* #6092
* #6096
* #6098
* #6097
* #6105
* #6104
* #6106
* #6109
* #6111
* #6112

Signed-off-by: Neil Twigg <neil@nats.io>
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.

3 participants