Skip to content
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

Uppy XHR upload - fails to load 10000 files. Page crashes. returns page reponsive error. #3313

Closed
mohandass-pat opened this issue Nov 11, 2021 · 4 comments
Assignees
Labels
Bug Stale Old issues that haven't had activity recently

Comments

@mohandass-pat
Copy link

Thank you for this amazing service. we are using Uppy for the last 6 months. It gives very much flexibility to our application requirements.

In our application we allow users to upload a large set of files (like google drive. we don't want to restrict users based on file count).

We are trying to upload 10k files in one go using Uppy XHR (png, 5kb - 20kb each). It works with Tus upload. but it crashes in XHR even before starts uploading. It fails to load in UI. We are using react Uppy. but we tried this on your example page also (https://uppy.io/examples/xhrupload/).

Here also
attached is the screenshot of the error on your example page.

Screenshot from 2021-11-11 19-29-08

@mohandass-pat mohandass-pat changed the title Uppy XHR upload - fails to load 10000 files. Page crashes. returns page reponsive error. Uppy XHR upload - fails to load 10000 files. Page crashes. returns page reponsive error. Nov 16, 2021
@aduh95 aduh95 self-assigned this Nov 22, 2021
@stale
Copy link

stale bot commented Nov 22, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale Old issues that haven't had activity recently label Nov 22, 2022
@stale stale bot closed this as completed Dec 10, 2022
@jaime-rivas
Copy link

First I'd like to add to @mohandass-pat in praising this project, we started using it recently and it's fantastic.

Secondly, I write to have it reopened since we are also experiencing this issue.

Third, I would like to suggest if it is possible to remove the bot that automatically closes issues. I think it's very important to see the number of open issues when evaluating its usage, and having issues automatically closed without resolution does not help the project. Thank you very much.

@aduh95
Copy link
Member

aduh95 commented Dec 12, 2022

Hi @jaime-rivas, thanks for the kind words :) I believe this issue is a duplicate of #2929, so while the stale bot was wrong in closing this for inactivity, I think it makes sense to leave this as close and subscribe to the other issue to track progress. FWIW it's on our TODO for this week.

Third, I would like to suggest if it is possible to remove the bot that automatically closes issues. I think it's very important to see the number of open issues when evaluating its usage, and having issues automatically closed without resolution does not help the project.

That seems fair enough, #4246 has been opened to make the bot never close issue – the label and the comment should be enough. Feel free to review the PR and give more feedback there if you feel it can be further improved.

@jaime-rivas
Copy link

Hi @aduh95, thank you very much for your responses. I look forward to contributing to this community :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Stale Old issues that haven't had activity recently
Projects
None yet
Development

No branches or pull requests

3 participants