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

🤖 tests: the extension.test.ts burst test times out on a busy host, and bun then does not exit

Open
  • Is something wrong?
#7,306 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bun, typescript
Domain
testing

Research direction

Start with the burst test and its until() helper in vscode/src/extension.test.ts; run the reported Bun command under load to reproduce the timeout and observe whether the process exits. Trace the test’s wait and cleanup path to identify why a timeout leaves the process alive. Done when the burst test tolerates busy hosts and a timeout does not hang the test process.

Written by the indexing model from the issue text.

Description

Summary

The test a burst of metadata events re-posts the list only when the projection changes in vscode/src/extension.test.ts sometimes hits its 5 s test timeout when the host is busy. After that failure, the bun process does not exit. A make test-unit run can then hang. This reproduces on main.

Runs

Command: bun test ./vscode/src/extension.test.ts ./scripts/perf/pageTimingCore.test.ts, capped at 120 s, load average about 8.

extension.test.ts from runs burst test timed out, then the process did not exit
main 2c4a5c444a 2 1
#7305 (only the onMetadata loop changes) 3 1

Each time the error lines were:

error: Test "a burst of metadata events re-posts the list only when the projection changes" timed out after 5000ms
(fail) chat view live workspace list and dock activity (#5109) > a burst of metadata events re-posts the list only when the projection changes [5000.99ms]

On #7305, the next test then failed with timed out waiting for the end of the burst from until() at vscode/src/extension.test.ts:96. The test's own 5 s until() timer lands in the next test.

What I know

  • The test builds 4,500 synthetic workspaces (vscode/src/extension.test.ts:513) and waits for 4 list posts with until(), which also has a 5 s timeout (:91-106, :538). The work fits in 5 s on an idle host and not always on a busy one.
  • I did not find what keeps the process alive after the timeout. A guess, not verified: the timed-out test skips its cleanup, so its subscription stays open.

Found while working on #7297 (#7305).

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

Dominant language
TypeScript
Stars
2.1k
Forks
140
Avg merge
4h 57m
Merged PRs (30d)
946

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.