DOC: document Context#perform_microtask_checkpoint#419
Merged
Conversation
Adds a "Microtask checkpoints" section explaining V8's auto-drain behavior and when manual draining is needed (Ruby callbacks invoked synchronously from JS, e.g. chained dispatchEvent listeners). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
|
CI failure is strange, it just skipped 3 specs ... not exit 1 worthy. |
Collaborator
|
@SamSaffron in #417 I noticed that Ruby 3.1 consistently seems to hang in CI. The other failures are more intermittent and might also be some Github issues? 🤷 |
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
3 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.
Follow-up to #418 as requested.
Adds a Microtask checkpoints subsection to the README:
Promise.resolve().then(...)"just works" for simple scripts).Context#perform_microtask_checkpointand when you actually need it — the synchronous-Ruby-callback case (e.g. chaineddispatchEventlisteners running in onecontext.call).mini_racerlocally; outputs in the comments are real.Placed after Function call, before Performance, matching the existing flat h3-section pattern in that area. Kept the section short given your note about README size.
🤖 Generated with Claude Code