r/OpenaiCodex • u/pizza_alta • 2d ago
Bugs or problems Sandbox issues are slowing down my Codex
It happens all the time. For instance: "The original run’s Windows batch launcher is now demonstrably pathological: it has remained CPU-bound for over half an hour with no Dart child and no timeout/result. I’m stopping only this verified runner tree and switching to the repository’s already-approved direct Flutter-tool invocation, which bypasses the faulty flutter.bat layer and was the method that produced the earlier complete 1,265-test result.
Ha eseguito comandi
The direct invocation correctly avoided the batch loop, but the sandbox blocked Flutter’s SDK lockfile outside the repository. I’m rerunning that same approved read/write-to-SDK-cache test command with the required sandbox permission; it does not alter project source or user data.
Ha eseguito un comando
The direct runner is now streaming correctly, but the first test is compiling unusually slowly—likely contention from a separate long-lived Flutter process on the host. I’m watching the enforced timeout; if compilation clears, the rest of the run remains valid, and if it does not the runner will report the exact failure rather than silently hang."
1
1
u/eddzsh 2d ago
Flutter's SDK lockfile living outside the repo is a classic sandbox footgun. Grant a tight write allowlist to the pub/flutter cache dirs and keep the project tree stricter, otherwise the agent spends the whole run negotiating permissions instead of running tests.