We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected behaviour
Large download from FS is streamed (or equivalent) successfully.
Current behaviour
Large download from FS ends up loading the large file into memory, causing it to throw a 502 status code.
Steps to reproduce
Solution
A temporary fix to this issue that currently fits our need is to change the HttpResponse to a StreamingHttpResponse here: https://github.com/artefactual/archivematica/blob/qa/1.x/src/dashboard/src/components/helpers.py#L269
To my understanding (and unfortunately) this would cause a Django worker to be blocked while streaming.
Your environment (version of Archivematica, operating system, other relevant details)
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behaviour
Large download from FS is streamed (or equivalent) successfully.
Current behaviour
Large download from FS ends up loading the large file into memory, causing it to throw a 502 status code.
Steps to reproduce
Solution
A temporary fix to this issue that currently fits our need is to change the HttpResponse to a StreamingHttpResponse here:
https://github.com/artefactual/archivematica/blob/qa/1.x/src/dashboard/src/components/helpers.py#L269
To my understanding (and unfortunately) this would cause a Django worker to be blocked while streaming.
Your environment (version of Archivematica, operating system, other relevant details)
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered: