[
https://issues.apache.org/jira/browse/SLING-13268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18098479#comment-18098479
]
Robert Munteanu commented on SLING-13268:
-----------------------------------------
[~daim] - assigning to you as discussed offline.
> PartialReader section slicing breaks when Reader.skip() returns 0
> -----------------------------------------------------------------
>
> Key: SLING-13268
> URL: https://issues.apache.org/jira/browse/SLING-13268
> Project: Sling
> Issue Type: Bug
> Reporter: Rishabh Daim
> Assignee: Rishabh Daim
> Priority: Major
>
> h3. Summary
> PartialReader assumes a single Reader.skip(startCharIndex) fully advances to
> section start.
> With commons-io 2.22.0 behavior exposure, section boundaries can shift.
> h3. Impact
> Schema aggregation may leak raw section headers (QUERY:/TYPES: separators)
> into SDL and break GraphQL parsing.
> h3. Fix
> Skip robustly until the requested offset is reached (or EOF), instead of
> relying on one skip() call.
> h3. Reproducer
> Unit test with a Reader whose skip() returns 0 reproduces the bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
