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
Data synchronization accidentally deletes local files #9631
Comments
你好,感谢提供日志,卡住的问题暂时没有找到。删除的问题是云端同步删的,还记得 14:07 到 14:11 分之间有使用过其他设备同步吗? |
没有,很确定当时只有这一个设备在运行。
…---原始邮件---
发件人: ***@***.***>
发送时间: 2023年11月11日(周六) 晚上9:27
收件人: ***@***.***>;
抄送: ***@***.******@***.***>;
主题: Re: [siyuan-note/siyuan] 思源卡住,强制关闭后,刚添加的数据库被删除 (Issue #9631)
你好,感谢提供日志,卡住的问题暂时没有找到。删除的问题是云端同步删的,还记得 14:07 到 14:11 分之间有使用过其他设备同步吗?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
收到,我再分析看看,多谢。 |
已经找到原因了,是因为下载云端快照文件时存储服务返回了旧的快照文件,但同步算法假设这是最新的,导致合并时删除了本地文件。 根本的原因我们已经发工单咨询存储服务提供商,还需要一些时间排查,谢谢。 |
88250
changed the title
思源卡住,强制关闭后,刚添加的数据库被删除
Data synchronization accidentally deletes local files
Nov 12, 2023
已经找到一个解决方案,但需要上线测试进行验证,请后续帮忙留意修复情况,谢谢。 |
88250
added a commit
to siyuan-note/dejavu
that referenced
this issue
Nov 12, 2023
88250
added a commit
to siyuan-note/dejavu
that referenced
this issue
Nov 12, 2023
88250
added a commit
that referenced
this issue
Nov 12, 2023
88250
added a commit
to siyuan-note/dejavu
that referenced
this issue
Nov 12, 2023
88250
added a commit
that referenced
this issue
Nov 12, 2023
88250
added a commit
to siyuan-note/dejavu
that referenced
this issue
Nov 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
思源卡住,强制关闭后,刚添加的数据库被删除
Is there an existing issue for this?
Can the issue be reproduced with the default theme (daylight/midnight)?
Could the issue be due to extensions?
Describe the problem
图1是添加的记录
图2是被删除的记录
Expected result
D大帮忙看下,卡住的原因和数据被删除的原因。
Screenshot or screen recording presentation
No response
Version environment
Log file
siyuan.log
More information
No response
The text was updated successfully, but these errors were encountered: