Conversation
…forwarded role (lidge-jun#5334 follow-up) lidge-jun#5334 made the developer wire role tri-state: an undeclared destination folds it to system. Two suites asserting role:"developer" on the Chat wire were missed because they are about tool-result repair ordering and document parts, not role selection — declare the destination, per the convention the change established. Verified: both files fail on dev@600075d2 with system-for-developer wire roles and pass with the declaration. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository: luvs01/opencodex/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 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. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…pair Co-Authored-By: Epinephrine <luvs01@hanmail.net>
|
Fixed in 67ccd8d — |
1 similar comment
|
Fixed in 67ccd8d — |
|
Consolidated into lidge-jun#5560 as a single related-function aggregate. Source head: Both stateful-continuation implementation 4edc411 and independent reasoning-cleanup follow-up 67ccd8d match carried 82a5f6d and aac783f by stable patch IDs, with original authors retained. The shared f700 role-fixture correction is already present in dev, with both exact provider objects carrying foldDeveloperRoleToSystem:false. All source changed-file occurrences were accounted for; the final composed adapter preserves upstream-owned output-only calls while independently stripping unrecoverable reasoning, and the new capability matrix covers those combinations. Focused evidence totals 377 distinct passing cases; types, structure, privacy and 497-page docs build passed. The broader changed run exited124 at900s with unresolved partial failures and is explicitly not green. This retires only this owner-controlled duplicate review entry; other contributors' upstream originals remain OPEN. Full suite, cross-platform CI, provider acceptance and security review remain on the draft proposal. Closing this duplicate standalone review entry as part of the requested consolidation after verifying coverage. This is not a merge or release claim; remaining integration checks and reviews are tracked on the replacement. Original branches are retained. |
Motivation
function_call_output/custom_tool_call_outputitems to be rewritten into user messages when the matchingfunction_callstill lived upstream behindprevious_response_id.Description
repairOrphanedInputItemsby introducing arepairOrphanOutputsparameter so orphan-output-to-user-message conversion can be toggled, and preserve the original signature-compatible behavior when enabled (src/adapters/openai-responses/tool-output-recovery.ts).repairOrphanedInputItemswithrepairOrphanOutputsenabled only when appropriate (forward or stateless wires, or when there is no unexpandedprevious_response_id) (src/adapters/openai-responses/passthrough.ts).tests/providers/xai/xai-responses-adjacency.test.ts).structure/providers/chat-compat.md).Testing
bun test tests/providers/xai/xai-responses-adjacency.test.tsand related focused dangling-call suites; the focused set passed (8–25 tests depending on scope) on the repo Bun (node_modules/bun/bin/bun.exev1.4.0).bun x tsc --noEmitand structure SSOT checks withbun run structure:check; both succeeded.tests/providers/xai/xai-responses-adjacency.test.ts,tests/responses/responses-forward-dangling-call.test.ts, andtests/responses/responses-stateless-dangling-call-repair.test.ts; these passed end-to-end in the environment used.bun run testin this container showed unrelated environment/timing/process-group flakes in other suites; the changes in this PR are covered by the focused tests which passed.Codex Task