You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
buffer: fill ignores an explicit end when offset is undefined #67574
The buf.fill documentation gives offset a default of 0 and defines end as the exclusive stopping position. Defaulting offset should preserve the explicitly supplied end, giving the same result as offset=0.
In _fill, the undefined-offset branches set both offset=0 and end=buf.length. The reproduction keeps end within bounds to isolate this behavior.
AI tools assisted with analysis and preparation of this report and its reproduction. A human has reviewed and confirmed the issue and verified that it is reproducible.
Activity
buffer: fix fill ignoring explicit end when offset is undefined
buffer: fix fill ignoring explicit end when offset is undefined
inoway46 commentedon Nov 22, 2026
Reproduced on main (v28.0.0-pre), v26.13.1, and v24.22.3 (macOS arm64).