[codex] Verify app-server process cwd execution#28137
Draft
Conversation
1d3f4ce to
dd8d90d
Compare
8122ee5 to
ce2887a
Compare
dd8d90d to
09e1c35
Compare
ce2887a to
0888dd7
Compare
This was referenced Jun 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close the app-server integration gap where every
process/spawntest supplied a cwd but none proved the child used it.Create a separate process directory with a marker, execute a relative read through
process/spawn, and deep-compare the exit notification and output on Unix and Windows.The focused test, full
process_execintegration module, andjust fix -p codex-app-serverpass.