Handle Slack msg_too_long by posting tail in thread#132
Merged
seratch merged 1 commit intoDec 29, 2025
Conversation
When chat.update hits msg_too_long, post only the remaining tail in the same thread to avoid truncation and repetition. Track last-sent prefixes and final-send claims to prevent duplicate replies, and cover long-reply paths with tests.
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
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.
When chat.update hits msg_too_long, post only the remaining tail in the same thread to avoid truncation and repetition. Track last-sent prefixes and final-send claims to prevent duplicate replies, and cover long-reply paths with tests.
GitHub Copilot summary: