Fix Fiber::ExecutionContext::Isolated#wait must suspend fiber#15720
Merged
straight-shoota merged 1 commit intocrystal-lang:masterfrom Apr 28, 2025
Conversation
ysbaddaden
added
the
kind:bug
straight-shoota
approved these changes
Apr 28, 2025
Qard
approved these changes
Apr 28, 2025
straight-shoota
changed the title
Fiber::ExecutionContext::Isolated#wait must suspend fiber
Collaborator
|
Successfully created backport PR for |
straight-shoota
pushed a commit
that referenced
this pull request
Apr 28, 2025
…) (#15723) Co-authored-by: Julien Portalier <julien@portalier.com>
1 task
Contributor
|
Can confirm that this solves the issue on 1.16.2. Thank you for your incredibly fast solution! <3 |
ysbaddaden
deleted the
fix/execution-context-isolated-wait-must-suspend-fiber
branch
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
5 participants
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.
Closes ysbaddaden/execution_context#39 as reported by @BigBoyBarney.