[5693] fix(backend): report Codex in runner health - #5716
Conversation
|
@huige66631 is attempting to deploy a commit to the agenta projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Hi @huige66631, thanks for opening a pull request. 🙏 This PR was automatically closed because it does not yet meet our contribution requirements:
We ask for this so every change is documented and demonstrably tested before review. How to get it reopened See the Contributing guide and Creating your first PR. If you think this was closed in error, leave a comment and a maintainer will take a look. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Disabled knowledge base sources:
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe runner now includes ChangesCodex health reporting
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Context
The runner's
/healthendpoint omittedcodexfrom theharnesseslist, even though Codex runs are supported. The response therefore under-reported the runner capabilities.Changes
Add
codextoHARNESS_KINDS, the source used to build the health response. Extend the/healthunit test to assert that the returned harness list includescodex.Fixes #5693
Tests / notes
corepack pnpm exec vitest run --project unit tests/unit/server.test.tscorepack pnpm run typecheckgit diff --checkThe focused test and typecheck pass. The full suite was also attempted, but this Windows sparse checkout reports unrelated failures involving POSIX permissions, path separators, and cross-tree fixtures.