-
|
Updated from 2.5.4-1 to 2.5.9-1 and I experience new behaviour: any file modified is touched again after it is uploaded. (Previous behaviour experienced: no automatic change to local files if not edited elsewhere) I am in the process of going through issues, docs, discussions, and testing previous versions, but thought to "dump" my question here, to document it if nothing else, as there are several issues about this (#3110, #3124, #3146) and in all of them you, abraunegg, say that this is normal and expected behaviour, but also something about business accounts, and it also not a behaviour I previously experienced, so I would like to know: is touching file after upload expected behaviour in all cases? by "touch" I mean any sort of modification to the file on disk that was not initiated by the user. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
#3256 created a config file force_session_upload = "true"and now files are no longer modified after uploading, as desired. |
Beta Was this translation helpful? Give feedback.
-
This is 100% normal. Microsoft modifies your file post upload. All notion of file integrity is lost when you upload a file to Microsoft OneDrive as the platform adds metadata and changes the timestamp. This is a feature (IMHO a bug) that cannot be disabled. A 'session upload' gives you the opportunity to tell Microsoft OneDrive what the timestamp of the local file is, so Microsoft OneDrive uses that timestamp, rather than the one that it generates. A 'session upload' is used automatically when files are >4MB as per the API documentation. If the file you are uploading is changed in any way, the client will generally pull that file back down so that your local state is the same as what is online. Also, as an FYI, please do not close discussions. |
Beta Was this translation helpful? Give feedback.
@plu5
This is 100% normal.
Microsoft modifies your file post upload. All notion of file integrity is lost when you upload a file to Microsoft OneDrive as the platform adds metadata and changes the timestamp. This is a feature (IMHO a bug) that cannot be disabled.
A 'session upload' gives you the opportunity to tell Microsoft OneDrive what the timestamp of the local file is, so Microsoft OneDrive uses that timestamp, rather than the one that it generates.
A 'session upload' is used automatically when files are >4MB as per the AP…