I have noticed that renaming a file locally sets the file’s timestamp to the time of renaming the file instead of preserving the original timestamp.
Not sure if this bug was introduced recently or has been here the whole time.
Steps to reproduce (Linux command line):
- touch A # Creates a new file with the mtime T, uploads it to Google Drive with “modification time” set to T
- sleep 300 # Wait 5 minutes
- mv A B # Renames the file.
- Wait a few moments for the change to get synced and check B’s “modification time” on drive.google.com . The new file’s timestamp is now T+5 minutes instead of T. This is also reflected locally if the folder is unsynced and re-synced again.
Ubuntu Linux, insync v18.104.22.168839