[FIXED] Fix for a panic calculating record length for slotInfo when followed by dbit markers in idx. #5009
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.
This was reported by @piotrpio when trying to do a secure erase of a message the was followed by dbit markers which occur after compaction removes records from the raw msg block. The idx then expands via dbit markers for the idx slice.
Signed-off-by: Derek Collison derek@nats.io