[Bug]: resolveCodexRuntime test depends on the host's installed Codex
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, typescript
Research direction
Start with tests/codex-integration/codex-runtime.test.ts and run bun test --isolate tests/codex-integration/codex-runtime.test.ts on a machine with Codex CLI installed. Trace how the test resolves persisted and installed Codex versions and identify where host state enters the selection. Done means the test uses an isolated fixture and passes regardless of whether Codex is installed.
Written by the indexing model from the issue text.
Description
Client or integration
Other
Area
CLI
Summary
tests/codex-integration/codex-runtime.test.ts › resolveCodexRuntime › treats missing persisted and resolved versions as the same selection fails on clean origin/dev on a developer machine that has Codex installed. It expects "fallback" and receives "installed", so the test reads host state instead of an isolated fixture.
Reproduction
- On a machine with Codex CLI installed, check out clean
dev(dbb908f7d). bun test --isolate tests/codex-integration/codex-runtime.test.ts- One failure, the same on dev and on feature branches.
Version
dev dbb908f7d
Operating system
macOS 27 (darwin 27.0.0, arm64)
Provider and model
No response
Logs or error output
error: expect(received).toBe(expected)
Expected: "fallback"
Received: "installed"
(fail) resolveCodexRuntime > treats missing persisted and resolved versions as the same selection
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.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 7h 46m
- Merged PRs (30d)
- 638
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
-
[Bug]: Business Premium seat plan self_serve_business_prolite is counted at baseline capacity weight 1 instead of 5Possibly taken A pull request linked to this issue is open or already merged. Openaccount-pool bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lidge-jun/opencodex#7440 · 2 comments ·
Maintainers usually reply within 1 day
-
[Docs]: translate the #7395 OpenGateway and Mistral provider-guide sectionsPossibly taken @MannXo claimed this 2 days ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lidge-jun/opencodex#7405 · 3 comments ·
Maintainers usually reply within 1 day
-
account-pool enhancement needs-design proxy
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lidge-jun/opencodex#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Codex App hides dictation/voice when model_provider = "opencodex" (desktop 26.1016 capability gate)Openbug proxy
Difficulty 4/5 3-5 days Newbie friendliness 43/100
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Automattic/data-liberation-agent#953 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
funmary-app/funmary#399 ·
Maintainers usually reply within 1 day
-
area:curator enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
CassioDalla/Scrinalia#150 ·
Maintainers usually reply within 1 day
-
status: needs-triage v1-bug-bash
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
a2ui-project/a2ui#3533 ·
Maintainers usually reply within 1 day
-
backend enhancement priority:P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
geolens-io/geolens#3310 ·
Maintainers usually reply within 1 day