Skip to content

Send long Discord replies without truncation - #65

Merged
ldbumble merged 1 commit into
ldbumble:masterfrom
1cbyc:1cbyc/53-discord-reply-chunks
Sep 25, 2026
Merged

ldbumble merged 1 commit into
ldbumble:masterfrom
1cbyc:1cbyc/53-discord-reply-chunks

Conversation

@1cbyc

@1cbyc 1cbyc commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

What & why

Discord replies longer than 2,000 characters were sent once and silently truncated by the low-level sender. Split replies at 1,900 characters before sending so every character reaches the channel in order while short replies keep the existing single-send path.

Closes #53.

Testing

  • python3 -m pytest tests/test_reply_channels.py -q (13 passed)
  • python3 -m compileall -q taskuary/outbound.py tests/test_reply_channels.py
  • Full offline suite reached 5,285 passes and 5 skips; remaining failures were caused by unavailable optional dependencies and exhausted local disk, outside the changed reply path.

Checklist

  • Focused offline tests pass
  • New behavior has a test
  • No UI files touched
  • Existing user-facing channel contract is unchanged; the truncation bug is removed

Co-authored-by: insisong emmanuelisaacnsisong@gmail.com

Co-authored-by: insisong <emmanuelisaacnsisong@gmail.com>
@ldbumble
ldbumble merged commit dd98644 into ldbumble:master Sep 25, 2026
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.

Discord replies are cut off at 2,000 characters

2 participants