docs: document fiber scheduler concurrency - #357
Merged
Conversation
jbeckwith-oai
marked this pull request as ready for review
August 10, 2026 20:46
Contributor
HAYDEN-OAI
approved these changes
Aug 10, 2026
HAYDEN-OAI
left a comment
Contributor
There was a problem hiding this comment.
Overall looks good. The Async example and transport behavior line up; I left one low-priority wording clarification inline.
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
Net::HTTPtransport cooperates with an active Ruby fiber schedulerasyncusage example without introducing a runtime dependencyWhy
The SDK Surface Atlas classifies Ruby async support as a gap because the official SDK does not document a native path. The existing transport already uses scheduler-aware Ruby I/O, so this makes that behavior an explicit, tested SDK contract instead of adding a duplicate async client hierarchy.
Without an active scheduler, requests retain their existing blocking behavior.
Validation
mise exec ruby@4.0.6 -- ./scripts/test— 525 runs, 1,712 assertionsmise exec ruby@4.0.6 -- bundle exec rake lint:rubocop— 2,597 files, no offensesmise exec ruby@4.0.6 -- bundle exec rake typecheck