[Bug]: ocx-launcher-runtime "missing bundle reaches validated PATH Bun" times out at 5 s under host load
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, node.js, typescript
Research direction
Start with tests/cli/ocx-launcher-runtime.test.ts and the Node launcher PATH fallback activation test named in the report. Run that test file alone, then compare its timeout behavior with bun run test:changed under parallel suite load. Done when the test has a reliable timeout for its real Node and Bun subprocess work and passes in both runs.
Written by the indexing model from the issue text.
Description
Client or integration
Other
Area
Installation or packaging
Summary
tests/cli/ocx-launcher-runtime.test.ts › Node launcher PATH fallback activation › missing bundle reaches validated PATH Bun times out at the default 5000 ms when the host is busy, so bun run test:changed / bun run test reports it red. Run alone on the same tree it passes (77 pass / 0 fail, about 10.6 s for the file). The case spawns real Node and Bun processes, and that cost scales with host load, so a 5 s per-test budget is not reliable on a shared machine. I expected the case to either finish well inside its budget or have a budget that matches the subprocess work it does. I did not raise any timeout locally.
Reproduction
- On macOS with Node available, check out
131eae33b0(PR #7567's merge head; the launcher code comes from #7546 ondev). - While another full suite is running on the same machine (here another worktree's
bun scripts/test.tswith--parallel=4, load average about 6–9), runbun run test:changedwith Bun 1.4.3 as the runner. - The case fails with
^ this test timed out after 5000ms.(5121 ms). bun test tests/cli/ocx-launcher-runtime.test.tson the same tree passes.
Version
Commit 131eae33b0e8c4f5506592e8b51bc92c2defb15b (test runner Bun 1.4.3)
Operating system
macOS 27.0 (Apple silicon)
Provider and model
Not provider-specific.
Logs or error output
(fail) Node launcher PATH fallback activation > missing bundle reaches validated PATH Bun [5121.18ms]
^ this test timed out after 5000ms.
42446 pass / 110 skip / 2 fail — Ran 42558 tests across 1953 files. [402.92s]
Screenshots and supporting files
No response
Redacted configuration
No response
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
Found while validating #7567 (Refs #7525).
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 9h 39m
- Merged PRs (30d)
- 633
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lidge-jun/opencodex
-
catalog enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lidge-jun/opencodex#7704 · 1 comment ·
Maintainers usually reply within 1 day
-
bug streaming
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lidge-jun/opencodex#7720 · 2 comments ·
Maintainers usually reply within 1 day
-
bug gui platform
Difficulty 4/5 3-5 days Newbie friendliness 45/100
lidge-jun/opencodex#7716 · 1 comment ·
Maintainers usually reply within 1 day
-
account-pool provider provider-compatibility
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
catalog enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
lidge-jun/opencodex#7705 · 1 comment ·
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
a10y a10y-audit ai-driven-qa claude
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
linagora/twake-directory-manager#219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installsPossibly taken @zephyr91 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2393 ·
Maintainers usually reply within 4 days