fix(layers): Align reader observability#7687
Open
Xuanwo wants to merge 1 commit into
Open
Conversation
dosubot
Bot
added
size:L
suyanhanx
approved these changes
Jun 5, 2026
tisonkun
approved these changes
Jun 5, 2026
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.
Which issue does this PR close?
N/A.
Rationale for this change
After moving raw read ranges to readers, a few docs and observability layers still described or observed the old range-scoped read shape. This PR keeps raw fetch out of the backend contract and makes reader-side IO observable with range context.
What changes are included in this PR?
This updates the raw accessor docs and RFC-7660 text to describe
oio::ReadplusStreamRead/PositionReadadapters. It also propagates range information through logging, tracing, dtrace, and oteltrace reader wrappers, including streaming reads opened viaopen(range).Are there any user-facing changes?
No public API changes. Observability output for reader-side streaming reads now includes range context where supported.
AI Usage Statement
AI-assisted with GPT-5.