Skip to content

fix(async): linearize await inside catch for async fns/closures (#8681) #8707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
proggeramlug wants to merge 1 commit into from
Closed

fix(async): linearize await inside catch for async fns/closures (#8681) #8707

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/8707-await-in-catch-blockwait.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Fix a deadlock where an `await` inside a `catch` block of an async function or closure compiled to a blocking busy-wait instead of an async suspend. Reached re-entrantly from inside the async-step / async-generator pull cascade (a rejected awaited promise in a `try` routing to a `catch` that itself awaits — a common stream retry/cleanup shape), it monopolised the runtime thread and hung — the natively-compiled Claude Code `-p` streaming path being the motivating case. The async-step throw handler now routes the delivered error into the catch's already-linearized dispatch states (and lets a `throw` raised inside the catch escape correctly) instead of re-inlining the catch body as blocking awaits. (#8681)
Loading
Loading