Chinesezjc d3d66926fb fix(code-runtime): reject a maxWallMs above Node's maximum timer delay ... `config.maxWallMs` is only checked for positivity, and it is handed to `setTimeout`, which clamps any delay above 2^31-1 ms to 1 ms. A deployment configuring a 25-day wall ceiling therefore gets the opposite of what it asked for: every run times out on the first tick. The runtime now range-checks the field at load against MAX_TIMER_DELAY_MS from dsh-timeout and throws, so the misconfiguration fails loud where it is self-contained instead of silently inverting the budget. `computeMs` needs no matching bound: it is compared against measured event-loop utilization rather than fed to a timer. The test asserts both the rejection and that the boundary value itself loads.		2026-07-27 14:01:15 +08:00
..
bootstrap.spec.ts	fix(code-mode): generalize failures and bound diagnostics	2026-07-23 01:32:17 +08:00
built-lib.e2e.ts	fix(code-mode): generalize failures and bound diagnostics	2026-07-23 01:32:17 +08:00
output-json.spec.ts	test(code-runtime): type mutated array predicate	2026-07-23 03:11:53 +08:00
runtime.spec.ts	fix(code-runtime): reject a maxWallMs above Node's maximum timer delay	2026-07-27 14:01:15 +08:00
source-worker.compat.spec.ts	fix(code-runtime): flatten worker JSON transport	2026-07-22 19:09:27 +08:00
worker-json.spec.ts	test(code-runtime): cover malformed key markers	2026-07-23 03:09:13 +08:00