mirror of
https://github.com/pchuan98/codex.git
synced 2026-07-01 00:31:56 +08:00
Adam Perry @ OpenAI
9d938a46d9
## Why We want to make it possible for an app-server orchestrator on one OS to control an exec-server on another host running a different OS. In practice this kinda already works if you get lucky and the two hosts have the same path format, but we mangle quite a lot of operations if either end is Windows. This test starts exercising that interaction, although right now the initial bootstrap fails. Future changes will expand the test's assertions to match improved support. ## What Stacked on #27964. This adds a small Windows exec-server fixture and a Linux protocol smoke test using the reusable Wine harness, covering Windows environment discovery, non-TTY `cmd.exe` execution, output, exit status, and working directory. Once we've got the full codex binary cross-building under Bazel we could consider moving to the real binary instead of the stripped down exec-server-only binary used here.
19 lines
814 B
Rust
19 lines
814 B
Rust
//! Minimal Windows exec-server fixture for cross-platform tests.
|
|
//!
|
|
//! Keeping this wrapper separate avoids depending on the full Codex binary's
|
|
//! Windows cross-build, which is not yet supported by the Bazel graph. Linking
|
|
//! only the exec-server also makes the Wine test substantially faster to
|
|
//! iterate on.
|
|
|
|
use codex_exec_server::ExecServerRuntimePaths;
|
|
|
|
#[tokio::main]
|
|
async fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync>> {
|
|
let current_exe = std::env::current_exe()?;
|
|
// This fixture is always a Windows executable, so it neither invokes nor
|
|
// needs the separate Linux sandbox binary.
|
|
let runtime_paths =
|
|
ExecServerRuntimePaths::new(current_exe, /*codex_linux_sandbox_exe*/ None)?;
|
|
codex_exec_server::run_main("ws://127.0.0.1:0", runtime_paths).await
|
|
}
|