runtime: adopt merged stream lifecycle and cancellation semantics - #381
Merged
Merged
Conversation
lannbot
enabled auto-merge
September 16, 2026 23:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
a53b241, including #720 idle-drop and #721 tests), Wasmtime environ tocc546ee(#14342), and wasm-tools to 0.259.enter-sync-call, enforce synchronous instance-local progress, and publish real JSPI parks consistently before ordinary scheduler service. Timer handoff prevents infinite-yield background work from starving host continuations without deleting guest threads.Breaking changes
Runtime/translator move to plan format 6, and the four lockstep packages to 0.7.0. Old deploy-time plans/adapters must be retranslated, not relabeled. An actual format-5 linked-component fixture verifies rejection before execution. The protocol manifest and convention goldens are unchanged.
Getter/setter specification changes were reviewed; the pinned parser APIs still do not implement these forms, so this does not claim accessor support.
Verification
All
just gatesrecipes passed across the coordinated verification runs, including runtime/Rust/package tests, scheduler seeds, shell lanes, Chromium/Firefox page/worker/shared-worker and OPFS, and consumer smokes. The first runs stopped at migration lint leftovers and stale lane totals; those were corrected and the remaining/focused gates passed. JSC local lane is unavailable on arm64; required x64 CI covers it.One adjudicated supplementary conflict
Wasmtime's new
thread-transparency/reentrancyfixture expects an outer-instance thread to rescue a blocked synchronous Mid call. The pinned reference requires Mid-only candidates and an earlier synchronous-block trap. The assertion remains executed and its exact mismatch is classified under #380; no error equivalence or exclusion masks it. No new official-corpus exclusions were added.Related: #372, #380. Automerge will be armed after creation.