-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Blazor Support Large File Uploads #33638
Comments
@christophwille thanks for contacting us. Is the stream returning a 0 for the read coming from the InputFile component? |
|
@christophwille thanks for the additional details. @TanayParikh since you are fiddling with this area, can you give this a try? (Both with the improved implementation and with the old implementation in 5.0) |
Thanks for contacting us. We're moving this issue to the |
Looks like we have a hard limit of |
Is there a chance to lift this limit in either a point relase for v5 or v6 (I am selfish, WASM-only would be fine)? Edit: or make it configurable ("I know what I am doing"). But failing silently with 0 bytes is a very strange behavior. |
Will #33491 lift the limit mentioned in this issue or is this then still another different matter? (I'd be fine moving to Blazor 6 in this specific case, but if it is not gonna get lifted I need to switch to JavaScript) |
I've put up a proof of concept on what it'd take to implement large file support: #33900 |
Not having to resort to JS would be absolutely awesome! |
@TanayParikh What are the chances of this making it into preview7? |
That's still my target; need to merge the following PRs (pending review): |
@TanayParikh So this will ship in preview7 roughly mid-August, correct? For my understanding of how this will work: I can keep passing my desire max size to OpenReadStream and have nothing else to change, it will just work? |
Yep!
Exactly, the transition to this new underlying implementation should be entirely seamless on your end. Let me know if you run into any issues 😄 |
I have a working Blazor Web Assembly app that uploads files to Azure Storage (server provides SAS token urls, client upload to that destination). This works a-ok for "small" files the size of a couple 100MBs. However, I now have a 6.8GB file that doesn't - I am using bog standard code along the lines of the documentation:
For this large file, it returns immediately and creates a zero byte file on Azure Storage. I then tried this:
Surprisingly,
res
is0
so I see why the storage library would create a 0 byte file... but I don't get why Blazor behaves that way. (Note: I didn't test to see at what file size this behavior kicks in). I also didn't see anything that would indicate any sort of error. The stream simply isn't returning data.The text was updated successfully, but these errors were encountered: