-
Notifications
You must be signed in to change notification settings - Fork 10.8k
apply_patch fails everytime #13887
Copy link
Copy link
Closed
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appbugSomething isn't workingSomething isn't workingtool-callsIssues related to tool callingIssues related to tool callingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Metadata
Metadata
Assignees
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appbugSomething isn't workingSomething isn't workingtool-callsIssues related to tool callingIssues related to tool callingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Type
Fields
Give feedbackNo fields configured for issues without a type.
What version of the Codex App are you using (From “About Codex” dialog)?
0.108.0-alpha.12
What subscription do you have?
Go
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
The apply_patch/default file-edit function is unreliable in this Codex setup on Windows.
Observed behavior:
Creating test.md with apply_patch returned exit code 1 with no output, but the file was still created.
Updating the existing test.md with apply_patch returned exit code 1 with no output, and the file was not changed.
Multiline updates also returned exit code 1 with no output, and no changes were applied.
Direct shell-based file edits work, so general workspace write access is fine.
every time it failed patch step and then runs shell commands to solve that e
What steps can reproduce the bug?
NA
What is the expected behavior?
The apply_patch/default file-edit function is unreliable in this Codex setup on Windows.
Observed behavior:
Creating test.md with apply_patch returned exit code 1 with no output, but the file was still created.
Updating the existing test.md with apply_patch returned exit code 1 with no output, and the file was not changed.
Multiline updates also returned exit code 1 with no output, and no changes were applied.
Direct shell-based file edits work, so general workspace write access is fine.
every time it failed patch step and then runs shell commands to solve that e
Additional information
No response