-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix a memory leak when copying large files by using the hyrax uploader #960
Conversation
…r instead of a custom one
@@ -243,18 +243,14 @@ def update_file_set(attrs) | |||
def handle_remote_file(remote_file:, actor:, update: false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with these changes, update is an unused parameter. Do we still need it in the signature/calls?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, probably. I walked the code path and I think calling create_content all the time instead of sometimes calling update_content is the right call. You are attaching an unknowable file (remote source could change it) if you are downloading it from a url, so it makes sense to me that it has to be treated as new. I only have a confidence level of 72.5% on this though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
Co-authored-by: Shana Moore <shana.lavina.moore@gmail.com>
instead of a custom one