Closed momaek closed 3 months ago
I've fixed the issue by uploading a file to the server.
Argh...took me ages of unsuccessful searching until I found your fix. Works like a charm now! Thanks for sharing!
We need to fix this behavior.
I try to create a patch in order to avoid returning a 500 error. But it need tests from a new account.
When I initially setup rmfakecloud I don't remember encountering this, but that might be because I was using toltec. So all of my documents were marked for resync as part of configuring my rmfakecloud server https://github.com/toltec-dev/toltec/blob/7911eacd7256b0c813e496a41344757a7dcb2c2f/package/rmfakecloud-proxy/rmfakecloudctl#L76-L78
# Mark all files as not synced
grep sync "$xochitl_data_dir"/*.metadata -l \
| xargs sed -i 's/synced\": true/synced\": false/'
So the documents on my device were immediately uploaded on the first sync.
This error appears since the introduction of the /sync/v3/root
route, in v3.4.
I'll create a new account to test the patch, and use the command to mark all files are not synced. I think this should simulate the situation.
I've fixed the issue by uploading a file to the server.
WARNING: to anybody trying this: This will start a new sync and remove all existing Files from your device to replace them with the one uploaded to the server.
This will effectively wipe all your files. Happened to me :( After this, everything works fine :)
Thanks for the fix. Any chance we can get a release?
The expected answer is not a fake root, but a 404 with {"message":"root not found"}
.
I'll fix this and make a release.
Server system:
Alibaba Cloud Linux release 3 (Soaring Falcon)
Run in docker. Logs:Any ideas?