Skip to content

[wasmfs] FetchFS: fix getFileRange out-of-bounds issues #24442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented May 29, 2025

This change is authored by @foxtacles (See #24438)

Fixes: #24438


// Out of bounds. No request necessary.
if (start >= wasmFS$JSMemoryRanges[file].size) {
return Promise.resolve();
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can just use return here actually. See #24443

@foxtacles
Copy link

foxtacles commented May 31, 2025

More context: #24438 (comment)

I'd suggest holding off merging this until there's been more investigation. I'll update you as soon as I had the chance to dig further.

@sbc100 sbc100 marked this pull request as draft June 2, 2025 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FetchFS: getFileRange issues out-of-bounds chunk requests
3 participants