-
Notifications
You must be signed in to change notification settings - Fork 60.6k
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
[Bug] 同步始终有问题,谢谢 #4503
Comments
Title: [Bug] There is always a problem with synchronization, thank you |
感谢提出的建议,关于提到的问题,我们会尽快修复 |
Thanks for the suggestions. Regarding the mentioned issues, we will fix them as soon as possible. |
Should be no synchronization success, but the error is hidden by the underlying code, so the upper code shows synchronization success, there is a console error screenshot? |
#4507 |
#4507 |
谢谢答复,我更新了代码,现在提示了同步失败。 |
Thanks for the reply, I updated the code and now it says synchronization failed. |
现在这个同步逻辑是咋样的,我在本地搭建了NextWeb,webdav同步可用,但逻辑很奇怪,似乎总是从云端覆盖到本地。 |
What does this synchronization logic look like now? I built NextWeb locally, and webdav synchronization is available, but the logic is very strange, and it seems to always be covered from the cloud to the local. |
目前的逻辑是将云端的内容拉取下来与本地的进行merge,之后将merge的结果同步到云端 |
The current logic is to pull the content from the cloud and merge it with the local one, and then synchronize the merge results to the cloud. |
Calling api/upstash is a bug and has been solved in this PR #4525 |
更新了代码,还是同步失败。。。。 |
I updated the code, but the synchronization still failed. . . . |
Bug Description
1、webdav无法同步,显示同步成功,但是webdav网盘里始终是空。
2、upstash可以同步成功,能否添加自动同步功能?谢谢
Steps to Reproduce
1、webdav无法同步,显示同步成功,但是webdav网盘里始终是空。
2、upstash可以同步成功,能否添加自动同步功能?谢谢
Expected Behavior
1、webdav无法同步,显示同步成功,但是webdav网盘里始终是空。
2、upstash可以同步成功,能否添加自动同步功能?谢谢
Screenshots
No response
Deployment Method
Desktop OS
No response
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: