Help cloud to fix corrupted file "modificationTimeStamp"
Description
Some files on the cloud has invalid "last modified" timestamp (in second) with value of max of int32unsigned. This makes date for futur and is a kind of light corruption. We don't know exactly why it happens.
Infra team has a kind of routines to fix the files that regularly got the invalid value. It has been requested that eDrive also do some work to correct the situation.
So the eDrive part is about re-uploading file with correct timestamp and is implemented in this MR.
Technical details
-
Convert FileDiffUtils.java into kotlin -
Move FileDiffUtils.kt into 'contentScanner' package -
Write Unit Test for FileDiffUtils.kt -
Then fetch code idea from old MR !227 (closed) -
Improve fix idea -
Implement -
write unit test -
find how to test in real...resolve HTTPS certificate issue for local test or asked Infra team
Tests
In order to be able to test, as we don't have