You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't have a reproducible test case, but multi-part downloads incorrectly set the mtime of the file before closing it. This can cause the time to be reset to now when the file is closed.
I have a very simple patch to fix this issue as a pull request and have been running this patched version on our production servers since Nov 10.
Please do take a look so I don't have to keep my patch around.
Thanks, I'll take a look. One of the things we typically do before merging bug fix PRs is to try to get a test case written, both to ensure that a) the bug is confirmed fixed and b) we can prevent this bug from surfacing again. I'll try to see if I can get a test case written for this.
This is the original patch from @kirat-singh, but the forked
repo is no longer available.
I've added a unit test for this that shows that the mtime modification
is tied to the execution of an IOCloseRequest instead of the enqueuing
of the IOCloseRequest.
Fixesaws#1072Closesaws#994
Hi there,
I don't have a reproducible test case, but multi-part downloads incorrectly set the mtime of the file before closing it. This can cause the time to be reset to now when the file is closed.
I have a very simple patch to fix this issue as a pull request and have been running this patched version on our production servers since Nov 10.
Please do take a look so I don't have to keep my patch around.
#994
best,
-Kirat
The text was updated successfully, but these errors were encountered: