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

🤖 Mock AI error flows differ from real ones and add bug-bash noise

Open Beginner friendly
#5,700 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing-qa

Research direction

Start by reading mockAiStreamPlayer.ts and comparing its error handling with StreamManager.persistStreamError; done means the mock preserves the partial reply and error details. Then inspect buildRateLimitErrorReply in mockAiRouter.ts and the mock retry behavior; done means the mock supplies a Retry-After value consistent with the retry and allows Retry-After handling to be exercised.

Written by the indexing model from the issue text.

Description

enhancement

The mock AI (XUM_MOCK_AI=1) causes much of the noise in agent bug bashes (#5670):

  • mockAiStreamPlayer.ts deletes the partial reply on error and leaves an empty assistant row. StreamManager.persistStreamError keeps the partial with its error details. Matching it removes stray "[CONTINUE]" echoes and vanishing error banners.
  • The mock rate-limit error (buildRateLimitErrorReply in mockAiRouter.ts) sends no Retry-After, so its text says 60 seconds while the retry fires after 2 seconds, and the Retry-After handling cannot be exercised.

Priority P3. Size S each.

Found by the agent bug bashes in #5670 (pre-existing, outside that PR's changes).


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

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

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.