fix: keep work stopped under another supervisor token from returning after a Gateway crash (#201186) * fix(gateway): scope crash and child-completion restart recovery to the supervisor token OPENCLAW_GATEWAY_RESTART_RESUME_SCOPE scoped graceful-shutdown markers only. Work without a marker still came back under another token: a run orphaned by a crash, a parked yield, a legacy upgrade cycle, the queued input replayed after a crash, and a child completion that wakes its parent. Each accepted run now records the token it started under (at chat.send admission and at lifecycle start). Startup compares the marker's token, or the recorded one without a marker, before crash, parked and legacy recovery and before taking back completion custody. Out-of-scope work is cleared without resuming; its queued input ends as restart-unrecoverable, and with a token set a session with no recorded token counts as out of scope. Recovered markers carry the token, so a second restart under it still resumes them. Without a token nothing changes. * test: run the restart resume scope test in the database worker pool * test: set the restart resume scope before the first database write * style: format the restart resume scope test
Current
·
C2
·2026-11
fix: keep work stopped under another supervisor token from returning …
Find Your Interest
- Android Systrace 基础知识 - SystemServer 解读
- Android Perfetto 系列 8:深入理解 Vsync 机制与性能分析
- Android Service:开发自己的通知中心(2):辅助***实战
- Android Perfetto 系列 15:Boot Trace、长时间现场 Trace 与偶发问题抓取
- Android Tools - Log2File
- Android Service:开发自己的通知中心(1):辅助***介绍
- Android 无障碍服务导致的整机卡顿案例分析
- This Week In Security: Four-Digit Patch Tuesday, SSH Exploited, GitBook Breach, Android GhostMap
- Android Perfetto 系列 5:Android App 基于 Choreographer 的渲染流程
- Android 基于 Choreographer 的渲染机制详解
Current
·
C2
·2026-11






