-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Remote Sync] Hardcoded wait timeout does not allow enough time #11234
Labels
Comments
I already knew that a hardcoded timeout is not a good idea 😅 |
:) no rush for me, I managed to build it with hardcoded 60 seconds (was a fun journey as it seems the docs for windows are a little outdated). Unfortunately I do not know c++ enough to actually create a pr to add the option. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The remote sync code has a hard coded 10 second wait time before killing the process. This is not long enough when the command is talking to a slower server which is performing multiple steps (protocol negotiation + database lookups + response time)
Please expose a configuration option for waitForFinished here and here
With this increased it is possible to sync with NextCloud using curl.
@t-h-e You have my thanks and appreciation for adding the one feature, holding me back from switching over. :)
Examples
Example commands for syncing with NextCloud using a directory shared with a password:
download:
upload:
The text was updated successfully, but these errors were encountered: