云端数据损坏的一种复现方式

最近发现我每次打开思源的时候，都提示我云端数据损坏，但是当我连通网络的时候，一切又恢复正常，感觉像是误报

之前一直在工作室使用这种方式上网，为什么说最近才会发生呢？因为最近天翼校园网好像更新了（也许不是这个原因，但大概率），我发现之前自动登录校园网的脚本也失效了

环境

1. 处于学校内网环境，默认是不与外网相通
2. 我们工作室只有一个校园网账号，所以我们通过路由器登录校园网，然后我们连接路由器的 wifi 来登录校园网
3. 天翼校园网
4. 思源版本：v3.1.31

稳定复现步骤

1. 首先我们的思源是可以正常同步的

2. 之后我们退出思源笔记（只有首次进入思源才会提示云端数据损坏，使用过程中下线校园网的话是提示 网络超时）

3. 下线校园网

4. 再次启动思源笔记，发现提示云端数据损坏

   1. 

5. 登录校园网，恢复正常同步

视频

日志文件

     ___                                   ___           ___           ___
     /  /\        ___           ___        /__/\         /  /\         /__/\
    /  /:/_      /  /\         /__/|       \  \:\       /  /::\        \  \:\
   /  /:/ /\    /  /:/        |  |:|        \  \:\     /  /:/\:\        \  \:\
  /  /:/ /::\  /__/::\        |  |:|    ___  \  \:\   /  /:/~/::\   _____\__\:\
 /__/:/ /:/\:\ \__\/\:\__   __|__|:|   /__/\  \__\:\ /__/:/ /:/\:\ /__/::::::::\
 \  \:\/:/~/:/    \  \:\/\ /__/::::\   \  \:\ /  /:/ \  \:\/:/__\/ \  \:\~~\~~\/
  \  \::/ /:/      \__\::/    ~\~~\:\   \  \:\  /:/   \  \::/       \  \:\  ~~~
   \__\/ /:/       /__/:/       \  \:\   \  \:\/:/     \  \:\        \  \:\
     /__/:/        \__\/         \__\/    \  \::/       \  \:\        \  \:\
     \__\/                                 \__\/         \__\/         \__\/
I 2025/06/25 14:55:38 runtime.go:87: kernel is booting:
    * ver [3.1.31]
    * arch [amd64]
    * os [Microsoft Windows 10 Pro]
    * pid [20004]
    * runtime mode [prod]
    * working directory [C:\Program Files\SiYuan\resources]
    * read only [false]
    * container [std]
    * database [ver=20220501]
    * workspace directory [D:\CongSec]
I 2025/06/25 14:55:38 conf.go:129: loaded conf [D:\CongSec\conf\conf.json]
I 2025/06/25 14:55:38 conf.go:409: repo key [19278376ca15293ef76e300c65720dcbdf657401]
I 2025/06/25 14:55:38 conf.go:474: OpenAI API enabled
    userAgent=SiYuan/3.1.31 std/windows
    baseURL=https://api-s132j4w3s3y2t7b5.aistudio-app.com/v1
    timeout=30s
    proxy=
    model=deepseek-r1:70b
    maxTokens=1000
    temperature=1.0
    maxContexts=7
I 2025/06/25 14:55:38 conf.go:521: user has disabled [Google Analytics]
I 2025/06/25 14:55:38 runtime.go:139: use network proxy [system]
I 2025/06/25 14:55:38 serve.go:209: kernel [pid=20004] http server [0.0.0.0:6806] is booting
I 2025/06/25 14:55:38 working.go:545: database [D:\CongSec\temp\siyuan.db] size [342.28 MB]
I 2025/06/25 14:55:38 working.go:545: database [D:\CongSec\temp\blocktree.db] size [92.11 MB]
I 2025/06/25 14:55:38 working.go:545: database [D:\CongSec\temp\history.db] size [57.58 MB]
I 2025/06/25 14:55:38 working.go:545: database [D:\CongSec\temp\asset_content.db] size [1.07 MB]
I 2025/06/25 14:55:38 pandoc.go:146: built-in pandoc [ver=3.5, bin=D:\CongSec\temp\pandoc\bin\pandoc.exe]
I 2025/06/25 14:55:38 conf.go:1137: pandoc initialized, set pandoc bin to [D:\CongSec\temp\pandoc\bin\pandoc.exe]
I 2025/06/25 14:55:38 sync.go:146: sync before boot
W 2025/06/25 14:55:38 sync.go:1568: got empty cloud latest
I 2025/06/25 14:55:38 repository.go:1348: boot get sync cloud files elapsed [0.05s]
I 2025/06/25 14:55:38 repo.go:655: walk data [files=4141] cost [103.8516ms]
I 2025/06/25 14:55:38 ref.go:134: got local full latest [files=4141, size=799 kB], cost [3.0034ms]
I 2025/06/25 14:55:38 repository.go:1314: boot index repo elapsed [0.16s]
E 2025/06/25 14:55:38 repository.go:1359: sync data repo failed: cloud object not found
I 2025/06/25 14:55:38 conf.go:874: tree/block count [739/204697]
I 2025/06/25 14:55:38 working.go:224: kernel booted
I 2025/06/25 14:55:39 font.go:58: loaded system fonts [225] in [176ms]
I 2025/06/25 14:55:39 box.go:77: auto stat [trees=739, blocks=204697, dataSize=1.17 GB, assetsSize=1.11 GB]
I 2025/06/25 14:55:39 disk.go:33: disk usage [total=590.57 GB, used=452.98 GB, free=137.59 GB]
I 2025/06/25 14:55:39 publish.go:110: publish service [0.0.0.0:6808] is running
I 2025/06/25 14:55:42 sync.go:146: sync before boot
W 2025/06/25 14:55:42 sync.go:1568: got empty cloud latest
I 2025/06/25 14:55:42 repository.go:1348: boot get sync cloud files elapsed [0.08s]
I 2025/06/25 14:55:42 repo.go:655: walk data [files=4141] cost [103.5265ms]
I 2025/06/25 14:55:42 ref.go:134: got local full latest [files=4141, size=799 kB], cost [6.7168ms]
I 2025/06/25 14:55:42 repository.go:1314: boot index repo elapsed [0.20s]
E 2025/06/25 14:55:42 repository.go:1359: sync data repo failed: cloud object not found
W 2025/06/25 14:55:46 elevator_windows.go:101: not found elevator [C:\Program Files\SiYuan\resources\elevator\elevator-amd64.exe]
I 2025/06/25 14:55:56 cron.go:61: cron job [[RefreshRhyResultJob]] executed
I 2025/06/25 14:56:11 sync.go:146: sync before boot
I 2025/06/25 14:56:11 sync.go:1609: got cloud latest [device=2463533c-38a3-48ab-b7c5-5e72edcca29f/windows, id=5dafd595ae4dc4a94057d6264df596a0b92239a6, files=4141, size=1.17 GB, created=2025-06-25 14:54:22], cost [237.4128ms]
I 2025/06/25 14:56:11 repository.go:1348: boot get sync cloud files elapsed [0.24s]
I 2025/06/25 14:56:11 repo.go:655: walk data [files=4141] cost [104.4608ms]
I 2025/06/25 14:56:11 ref.go:134: got local full latest [files=4141, size=799 kB], cost [6.03ms]
I 2025/06/25 14:56:11 repository.go:1314: boot index repo elapsed [0.35s]
I 2025/06/25 14:56:15 repository.go:1430: syncing data repo [device=2463533c-38a3-48ab-b7c5-5e72edcca29f, kernel=h6cmgq7, provider=2, mode=a/true]
I 2025/06/25 14:56:15 repo.go:655: walk data [files=4141] cost [108.1794ms]
I 2025/06/25 14:56:15 ref.go:134: got local full latest [files=4141, size=799 kB], cost [4.8897ms]
I 2025/06/25 14:56:15 sync.go:1609: got cloud latest [device=2463533c-38a3-48ab-b7c5-5e72edcca29f/windows, id=5dafd595ae4dc4a94057d6264df596a0b92239a6, files=4141, size=1.17 GB, created=2025-06-25 14:54:22], cost [187.8361ms]
I 2025/06/25 14:56:15 repository.go:1502: synced data repo [device=2463533c-38a3-48ab-b7c5-5e72edcca29f, kernel=h6cmgq7, provider=2, mode=a/true, ufc=0, dfc=1, ucc=0, dcc=0, ub=0 B, db=178.38 kB] in [0.53s], merge result [conflicts=0, upserts=0, removes=0]

I 2025/06/25 14:56:15 index_fix.go:56: start checking index...
I 2025/06/25 14:56:17 index_fix.go:76: finish checking index
I 2025/06/25 14:56:17 store.go:61: purging data repo [D:\CongSec\repo\], retention indexes [208]
I 2025/06/25 14:56:19 store.go:242: purged data repo [D:\CongSec\repo\], [0] indexes, [0] objects, [0] bytes

附一个 AI 分析