[Withdrawn] Duplicate of #7658 — dsh_session_log watermark deadlock (HTTP 413 on long sessions)

[donyue7]

Withdrawn — duplicate report.

This was filed before checking the tracker. The same failure had already been reported several times, and its mechanism is already confirmed at code level:

• [Bug][Feature] 0.1.6 默认开启的 dsh_session_log 会让大型会话每次请求携带完整日志（本例 ~260 MiB）导致 TRANSPORT 死循环；建议改为默认关闭 + 首次启动显式征得同意 #6754 — 0.1.6 turned the session-log upload on by default (large request bodies, transport deadlock)
• [dsh_session_log] First upload carries the entire session log, permanently breaking long sessions with HTTP 413 #6862 — the first upload carries the entire session log
• 大会话分叉后所有请求永久 413：dsh_session_log 重传整份继承日志，撞上游约 50 MB 请求体上限 #7247 — a fork inherits the whole log (upstream body limit ≈ 50 MB)
• [Bug] 会话格式迁移后 dsh_session_log 水位失效：每次请求重发整份日志 → 413 且永久卡死 #7658 — watermark invalidation after migration; confirmed at HEAD (session-log-deepseek/src/index.ts:136)

The incremental evidence this report carried — a machine-verified default diff (enabled: false in 0.1.5-rc.2 → enabled: true in 0.1.7-rc.1), the "watermark was never established" measurements, and a workaround verified end-to-end after a restart — has been contributed under #7658. The generalised guardrails are proposed in #7737.

Please follow those two threads; this one can be ignored or removed by a maintainer.