Skip to content

Sync access to web socket continuations #633

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.

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

Merged
merged 2 commits into from
Mar 17, 2025
Merged

Conversation

pblazej
Copy link
Contributor

@pblazej pblazej commented Mar 14, 2025

Resolves #528

Turning WebSocket into an actor would do more harm than good (nonisolated deinit, nonisolated requirements). Nullifying in the critical section is the only way to prevent double resume().

Copy link

ilo-nanpa bot commented Mar 14, 2025

it seems like you haven't added any nanpa changeset files to this PR.

if this pull request includes changes to code, make sure to add a changeset, by writing a file to .nanpa/<unique-name>.kdl:

minor type="added" "Introduce frobnication algorithm"

refer to the manpage for more information.

@pblazej pblazej requested a review from hiroshihorie March 14, 2025 12:49
Copy link
Member

@hiroshihorie hiroshihorie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice ✅

@pblazej pblazej merged commit f17581a into main Mar 17, 2025
20 checks passed
@pblazej pblazej deleted the blaze/socket-continuation branch March 17, 2025 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebSocket "SWIFT TASK CONTINUATION MISUSE" crash
2 participants