You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
tests: submit websocket turns with permission profiles - #20381
core/tests/common/test_codex.rs still exposed submit_turn_with_policy() helpers that converted SandboxPolicy into PermissionProfile before submitting turns. The websocket tests were the remaining callers, so they could exercise the same behavior directly through permission profiles.
Removing these helpers keeps new tests from accidentally reaching for the legacy sandbox abstraction when submitting Op::UserTurn.
What Changed
Updated websocket suite turn submission to call submit_turn_with_permission_profile() with the active test config permissions.
Removed submit_turn_with_policy(), submit_turn_with_policies(), and submit_with_policy() from the shared TestCodex helpers.
Preserved the existing compatibility helper that derives the required legacy sandbox_policy field from a PermissionProfile for direct Op::UserTurn construction.
Verification
cargo test -p codex-core websocket_first_turn_uses_startup_prewarm_and_create -- --nocapture
if !file_system.can_write_path_with_cwd(cwd, cwd){
returncustom_summary(network_enabled);
Classify bridged-incompatible root writes as custom permissions
summarize_managed_profile now labels any managed profile with writable roots and a writable cwd as workspace-write, but that misses profiles that write :root with carveouts (for example root write plus read-only exclusions). Those profiles are not representable as legacy workspace-write and were previously surfaced as custom permissions; with this change they are summarized as workspace-write [...], which misreports effective permissions in config/status output for custom profiles.
Closing this pull request because it has had no updates for more than 14 days. If you plan to continue working on it, feel free to reopen or open a new PR.
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
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.
Why
core/tests/common/test_codex.rsstill exposedsubmit_turn_with_policy()helpers that convertedSandboxPolicyintoPermissionProfilebefore submitting turns. The websocket tests were the remaining callers, so they could exercise the same behavior directly through permission profiles.Removing these helpers keeps new tests from accidentally reaching for the legacy sandbox abstraction when submitting
Op::UserTurn.What Changed
submit_turn_with_permission_profile()with the active test config permissions.submit_turn_with_policy(),submit_turn_with_policies(), andsubmit_with_policy()from the sharedTestCodexhelpers.sandbox_policyfield from aPermissionProfilefor directOp::UserTurnconstruction.Verification
cargo test -p codex-core websocket_first_turn_uses_startup_prewarm_and_create -- --nocapturejust fix -p codex-coreStack created with Sapling. Best reviewed with ReviewStack.