Repository navigation
Version Packages - #79
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🤖 auto-maintain reviewAutomated, advisory triage for
Review panel: 🟢 low highest severity run maintainer code review: 🟢 low
General code review: 🟢 low
QuickJS capability boundary: 🟢 low
Continuation and replay integrity: 🟢 low
Worker concurrency and resource limits: 🟢 low
Posted by auto-maintain. This automated code review is advisory; a human maintainer makes the call. |
|
@aayush-kapoor Can we get this in? I have fix that requires this and I would rather not pin the sha of the package |
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
run@2.1.8
Patch Changes
1b28a18: Add
limits.cpuTimeoutMs(default 10 seconds), which bounds the time the worker spends running guest JavaScript in one invocation. Time spent awaiting asynchronous host functions or blocked in synchronous host functions and module loaders does not count, and each continuation resume starts with a fresh budget. Exceeding it fails with the newRunCpuTimeoutError(RUN_CPU_TIMEOUT), even when an interruption is pending. The limit only takes effect when it is lower thantimeoutMs.This replaces the hidden 10,000 interrupt-check cap, which stopped long loops and large host-function workloads after about a second of guest work, regardless of
timeoutMs, and surfaced asRUN_TIMEOUTorInternalError: interrupted.timeoutMskeeps its meaning as the wall-clock ceiling for the whole invocation.@run/website@0.0.12
Patch Changes