Skip to content

ci: drop the OS_SANDBOX_HOOK_TIMEOUT_MS=10000 floor — redundant after ADR-0102 D1 - #3328

Merged
os-zhuang merged 1 commit into
mainfrom
claude/nested-write-sandbox-timeout-muw13i
Jul 20, 2026
Merged

ci: drop the OS_SANDBOX_HOOK_TIMEOUT_MS=10000 floor — redundant after ADR-0102 D1#3328
os-zhuang merged 1 commit into
mainfrom
claude/nested-write-sandbox-timeout-muw13i

Conversation

@os-zhuang

Copy link
Copy Markdown
Contributor

Follow-up to the ADR-0102 sandbox work (#3275). Removes the workflow-wide env: OS_SANDBOX_HOOK_TIMEOUT_MS: '10000' added in #3270.

Why it's now redundant

#3270 raised the sandbox hook budget across the whole CI workflow to paper over the #3259 flake: on an oversubscribed 4-vCPU runner, the fixed per-invocation WASM-creation cost alone tripped the 250ms wall-clock hook deadline while the VM was still progressing.

ADR-0102 D1 (#3301) changed the budget to script CPU-time: VM creation and idle host-await time are no longer charged. So the 250ms default is meaningful again on a loaded runner, and this global floor is dead weight.

This doubles as an end-to-end validation of D1

With the floor gone, the sandbox suite runs at the stock 250ms CPU budget on CI — including the nested-write integration tests (which were switched to the stock default in Phase 1). If Test Core stays green, that proves the #3259 flake is fixed at the root (VM-creation cost isn't charged to a CPU budget), not merely masked by a larger number.

  • Tests that assert a specific budget set it explicitly (hookTimeoutMs / body timeoutMs) and are unaffected.
  • Production always kept the 250ms/5000ms defaults; the OS_SANDBOX_*_TIMEOUT_MS / OS_SANDBOX_WALL_CEILING_MS env overrides remain available for constrained hardware.

Notes

  • CI-only config; no package change, no changeset.
  • Uses allow-major to bypass the unrelated pre-existing @objectstack/console: major changeset on main.

Please don't fast-merge — the point is to watch Test Core go green at the stock budget first.

🤖 Generated with Claude Code


Generated by Claude Code

@vercel

vercelBot commented Jul 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
specReadyReadyPreview, CommentJul 20, 2026 3:28am

Request Review

… ADR-0102 D1
#3270 raised the sandbox hook budget workflow-wide to paper over the #3259 load
flake: on an oversubscribed runner the fixed per-invocation WASM-creation cost
alone tripped the 250ms *wall-clock* hook deadline. ADR-0102 D1 (#3301) changed
the budget to *script CPU-time* — VM creation and idle host-await time are no
longer charged — so the 250ms default is meaningful again on a loaded runner and
this global floor is no longer needed. Removing it also validates the fix
end-to-end: the sandbox suite (incl. the nested-write integration tests, which
run at the stock default) must stay green at 250ms on CI. Tests that assert a
specific budget set it explicitly and are unaffected; production always kept
250ms/5000ms. The env override remains available for constrained hardware.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011iJLjqToxNv1aYP3syQtRp
@os-zhuang
os-zhuangforce-pushed the claude/nested-write-sandbox-timeout-muw13i branch from 68a1fbd to e9342a8CompareJuly 20, 2026 02:34
@os-zhuang
os-zhuang marked this pull request as ready for review July 20, 2026 02:49
@os-zhuang
os-zhuang merged commit 631deba into mainJul 20, 2026
14 of 15 checks passed
@os-zhuang
os-zhuang deleted the claude/nested-write-sandbox-timeout-muw13i branch July 20, 2026 02:49
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@os-zhuang@claude