From ef8b8ebc9430e3cdbc038bb80a606aaa224f3d75 Mon Sep 17 00:00:00 2001 From: Michael Bolin Date: Wed, 7 Jan 2026 16:36:23 -0800 Subject: [PATCH] fix: use tokio for I/O in an async function (#8868) I thought this might solve a bug I'm working on, but it turned out to be a red herring. Nevertheless, this seems like the right thing to do here. --- codex-rs/chatgpt/tests/suite/apply_command_e2e.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/codex-rs/chatgpt/tests/suite/apply_command_e2e.rs b/codex-rs/chatgpt/tests/suite/apply_command_e2e.rs index 2aa8b809b..7e096bce0 100644 --- a/codex-rs/chatgpt/tests/suite/apply_command_e2e.rs +++ b/codex-rs/chatgpt/tests/suite/apply_command_e2e.rs @@ -69,7 +69,7 @@ async fn create_temp_git_repo() -> anyhow::Result { async fn mock_get_task_with_fixture() -> anyhow::Result { let fixture_path = Path::new(env!("CARGO_MANIFEST_DIR")).join("tests/task_turn_fixture.json"); - let fixture_content = std::fs::read_to_string(fixture_path)?; + let fixture_content = tokio::fs::read_to_string(fixture_path).await?; let response: GetTaskResponse = serde_json::from_str(&fixture_content)?; Ok(response) }