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

🤖 tests: bug-bash harness notes from the #5721 final check

Open Beginner friendly
  • Is something wrong?
#5,746 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
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Start with tests/bugbash/reproSelection.ts to understand how make test-bugbash-repros locates each phase's report.json and how BUGBASH_REPRO_ARGS are used. Then review the caller lists in src/node/utils/agentToolsDisabled.ts and tests/bugbash/startApp.ts, along with the named workspace generators. Done when the output-folder behavior is documented or handled, and both comments accurately describe the callers.

Written by the indexing model from the issue text.

Description

backlog

Two non-blocking notes from the final readiness check of #5721 (bug-bash harness follow-ups). Neither affects CI or the safety claims.

  • --output in BUGBASH_REPRO_ARGS now fails the target. make test-bugbash-repros reads each phase's report.json from its fixed --output folder (tests/bugbash/reproSelection.ts). A user-supplied --output sends the reports elsewhere, so the selection check fails on a missing report. It fails loudly, not silently, but on main such an override worked. Fix: document "do not pass --output", or read the output folder from the arguments. Size S.
  • Incomplete caller list in two comments. src/node/utils/agentToolsDisabled.ts and the tests/bugbash/startApp.ts header list the callers that pass their own streamText tools and do not check XUM_DISABLE_AGENT_TOOLS. They leave out workspaceStatusGenerator.ts (propose_status) and workspaceTitleGenerator.ts (propose_name). Those tools only return structured output, so "none of them runs shell commands" still holds. Add them, or write "for example". Size XS.

Owner: the next change to tests/bugbash/.

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

Dominant language
TypeScript
Stars
2k
Forks
140
Avg merge
5h 59m
Merged PRs (30d)
935

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.