fix(format): prevent panic when thread has no replies in time range#600
Merged
rusq merged 1 commit intorusq:masterfrom Jan 28, 2026
Merged
Conversation
Add bounds check before slicing thread messages to handle edge case where thread parent exists but all replies are outside the archived time range. Fixes rusq#599
Owner
|
Thanks @ChrisEdwards ! |
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
2 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.
Summary
Fixes #599
When using
slackdump convertwith a time range filter, threads that have no replies within the specified time range cause a panic due to an out-of-bounds slice operation.The
getThreadfunction returnsmm[1:]to skip the parent message, but when there are no replies (only the parent or empty), this causes a panic.Changes
Test plan
slackdump convertwith a time range that excludes thread replies