Je fais la mise à jours :
Ensuite j’ai listé tous mes fichiers :
$ ls -l -h -R * > list_29102018.txt
Puis j’ai voulu voir si cette mise à jours m’avait ajouter des fichiers conflicts :
grep « conflict-2018-10-29T20 » list_29102018.txt | wc -l
41
J’ai donc 41 nouveaux fichiers en conflits qui ont étés crées suite à cette mise à jours (logs à disposition !) … je craque . Je pense que Cozy Cloud n’est pas pour moi … c’est une usine a corrompre les noms des fichiers. Je pense que je reviendrais quand cela sera plus stable.
Dans les logs j’ai pu lire :
{"message":"Cannot read property '_rev' of undefined","name":"TypeError","stack":"TypeError: Cannot read property '_rev' of undefined\n at Remote.moveFileAsync (/Applications/Cozy Drive.app/Contents/Resources/app.asar/core/remote/index.js:208:34)\n at "}
A noter aussi des erreur du type:
"err":{"message":"{\"errors\":[{\"status\":\"412\",\"title\":\"Precondition Failed\",\"detail\":\"Revision does not match\",\"source\":{\"parameter\":\"If-Match\"}}]}","name":"FetchError","stack":"FetchError: {\"errors\":[{\"status\":\"412\",\"title\":\"Precondition Failed\",\"detail\":\"Revision does not match\",\"source\":{\"parameter\":\"If-Match\"}}]}\n at handleResponse (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/fetch.js:92:15)\n at /Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/fetch.js:17:29\nFrom previous event:\n at /Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/fetch.js:17:17\n at runCallback (timers.js:781:20)\n at tryOnImmediate (timers.js:743:5)\n at processImmediate [as _immediateCallback] (timers.js:714:5)\nFrom previous event:\n at cozyFetch (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/fetch.js:7:30)\n at fetchJSON (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/fetch.js:78:10)\n at cozyFetchJSON (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/fetch.js:53:10)\n at doUpdateAttributes (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/files.js:186:10)\n at updateAttributesById (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/files.js:194:10)\n at Object.prototyped [as updateAttributesById] (/Applications/Cozy Drive.app/Contents/Resources/app.asar/node_modules/cozy-client-js/dist/webpack:/src/index.js:307:12)\n at RemoteCozy.updateAttributesById (/Applications/Cozy Drive.app/Contents/Resources/app.asar/core/remote/cozy.js:116:30)\n at Remote.moveFileAsync (/Applications/Cozy Drive.app/Contents/Resources/app.asar/core/remote/index.js:211:63)\n at "},
A noter que pour avoir le nom du fichier le plus long, je fais la commande :
$ grep « ^\-rw » list_29102018.txt | awk ‘{ print $9}’ | awk ‘{ print length, $0 }’ | sort -n | cut -d » » -f2- | tail -1
etickets_158406-conflict-2018-07-24T06_10_12.707Z-conflict-2018-07-25T10_02_12.673Z-conflict-2018-07-26T07_34_52.260Z-conflict-2018-07-27T08_35_00.500Z-conflict-2018-07-30T05_45_48-conflict-2018-10-29T20_58_47.038Z.pdf
j’ai donc 6 conflicts … Misère.