fix(codex): preflight sync injection before catalog writes - #1461
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthrough
ChangesCodex preflight and synchronization
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested reviewers: Sequence Diagram(s)sequenceDiagram
participant CLI
participant Injector
participant CatalogCache
participant CodexHome
CLI->>Injector: Run validation-only injection
Injector-->>CLI: Return success or concrete failure
alt Validation succeeds
CLI->>CatalogCache: Refresh catalog and cache
CLI->>Injector: Run final injection
Injector->>CodexHome: Write Codex configuration artifacts
else Validation fails
CLI-->>CodexHome: Preserve existing catalog and cache
end
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 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 |
|
✅ Deterministic PR hygiene checks passed. |
9e5cc13 to
d6dad87
Compare
|
Exact-head CI review complete for The changed sync/injection path remains green locally (16 focused tests, typecheck, privacy scan, diff check). GitHub gates, service checks, macOS, packaging, keyring, API/storage jobs, and Linux shards 1/2 passed. The remaining red jobs are repeatable Bun 1.3.14/runner failures, not product assertions:
I am not changing the product patch to accommodate this runtime failure and will not churn a third identical rerun. The PR remains draft for independent review/integration; no merge was performed. |
d6dad87 to
9c9ca09
Compare
Inventory all seven bug-labelled issue/PR pairs against dev 87e3ff9, record each reviewer blocker and red-CI root cause, and write one decade doc per pair. Audit findings beyond the filed reviews: - #1462 (no review yet) still resurrects a deleted provider or custom model when the stale process also edited that row: a persisted MISSING_CONFIG_VALUE is not a plain record, so src/config.ts:2884-2896 skips recursion and live wins. Probed at the exact head, both entity types came back. - #1465 (no review yet) gets its two-phase ordering right, but rollback deletes the scheduler task by name without proving this attempt created it, so a concurrent registration can be destroyed by our cleanup. - #1441's three blockers are already addressed on current head aa256f6; the reviewer judged the older, replaced head a8087d3. - #1461 and #1441 red CI is infrastructure noise (Bun 1.3.14 segfault and epoll_ctl EEXIST, plus the #1302 shard hang), not a contributor regression. Refs #1459 #1453 #1273 #1454 #1449 #1439 #1429
Summary
Closes #1453
Exact-head verification
dev@20c513198e4ef943fa990decad21fff92f3cfad49c9ca092a19b8e21c8d4b8aebaa91c10f1b4a3d2bun test tests/codex-sync-api.test.ts tests/cli-restore-back.test.ts— 16 passedbun run typecheck— passedbun run privacy:scan— passedgit diff --check— passedcicheck is red.The same patch on the immediately preceding
dev@87e3ff9f6base also built all 221 documentation pages. Its local full suite reached 10,930 passed and 11 skipped, with no assertion failure in the changed sync/injection path.The exact-head shard-4 log failed before the affected sync/injection tests: Bun 1.3.14 raised
EEXIST: file already exists, epoll_ctlwhile loadingtests/catalog-oauth-observation.test.ts, followed byCannot call beforeEach() after the test run has completed. The runner then stopped producing test output after starting an unrelated Claude Desktop config-path test until the 15-minute limit cancelled it and Actions terminated an orphanbunprocess. The preceding code-equivalent runs hit the same Bun loader failure and dangling-process family on other Linux shards. No product assertion failed in the changed path, and no product code was changed to accommodate the runner defect; the PR remains draft pending independent review and a green required aggregate.Checklist
Summary by CodeRabbit
ocx syncnow validates managed Codex configuration before making changes.ocx restore backapplies the same safety checks before re-enabling routing.