Backport #4421: fix(core): don't strand runs on throttled writes past the delivery ceiling or in QuickJS inline claims - #4437
github-actions[bot] wants to merge 1 commit into
Conversation
…iling or in QuickJS inline claims (#4421) * fix(core): don't strand a run on throttled writes past the delivery ceiling or in QuickJS inline claims * fix(core): gate throttled-step stepInput on the CBOR queue transport * fix(core): defer a replay for a throttled QuickJS inline step, like the node engine Signed-off-by: Nathan Rajlich <n@n8.io>
🦋 Changeset detectedLatest commit: f3cea21 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Closing as superseded by #4422, which targets |
Automated backport of #4421 to
stable(backport job run).AI recommendation: Both halves are stability fixes, not feature work: the run stranded
runningwith no queue message left to drive it after a transient (429/5xx/transport) failure of the max-deliveriesrun_failedwrite. That give-up path exists verbatim onstable(packages/core/src/runtime.tsaround the "Failed to mark run as failed after ... delivery attempts" log, withisRetryableWorldErroralready imported), so theruntime.tsfix and itsruntime.test.tscoverage apply directly. The QuickJS half (packages/core/src/runtime/quickjs-entrypoint.tsand its new test) is main-only — that file is absent onstable— so those hunks should simply be dropped during the cherry-pick along with their changeset.Merge conflicts were resolved by AI (opencode with
anthropic/claude-opus-5). Please review the conflict resolution carefully before merging.