Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🤖 Compaction follow-up dispatch: remaining follow-ups from #5313

Closed
  • Is something wrong?
#5,333 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@ThomasK33 is already working on this.

Since Sep 30, 2026.

Assessment

This issue has not been assessed yet.

Description

Tracking issue for the follow-ups listed in the #5313 PR body (compaction follow-up dispatched once, formal/compaction/).

  1. Add a test for the archive branch of the C1 fix (an edit must not re-arm the follow-up).
  2. Reuse leavesCompactionFollowUpPending in dispatchPendingFollowUp, instead of duplicating the pending check.
  3. Give the duplicate-identity refusal its own log reason, so it can be told apart from other refusals.
  4. Check whether the deleteMessage paths can re-expose a compaction summary that was already consumed.

Related: #5326 (MessageQueue: held sends vs an orphaned compaction decision).

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $37.39

Dominant language
TypeScript
Stars
2k
Forks
139
Avg merge
6h 22m
Merged PRs (30d)
858

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/xum

All issues in coder/xum

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.