fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: correct the canary commit hash after dropping an unrelated submodule change

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE
This commit is contained in:
Sylpheed RE agent
2026-08-24 02:31:03 +00:00
parent 4b6b72ca7b
commit 61acc81b3c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/re/mission-freeze-resume-spin.md
View File

@@ -339,7 +339,7 @@ because the boot was not going to finish.
## ✅ 2026-08-24 (later) — the instrument exists: `--log_stuck_waits`
Canary branch **`auto/re-wait-timeout-probe`** (`83ad0eb3f`, off the upstream
Canary branch **`auto/re-wait-timeout-probe`** (`820696c11`, off the upstream
baseline) adds a counter in `xeKeWaitForSingleObject`: consecutive `X_STATUS_TIMEOUT`
results on the **same object**, per thread, logged at 100 and then every 500.
It is self-selecting — a wait that is being satisfied never builds a streak — so