会话锁报错“storePath undefined”时的修复与验证清单（PR #14755）
问题/场景：部分会话在并发写入时可能触发 withSessionStoreLock 对未定义 storePath 的异常。前置条件：你运行的是多会话或高并发场景。实施步骤：升级到包含 PR #14755 的版本、复现旧问题、观察锁路径是否稳定并核对无崩溃。关键命令：`openclaw gateway status`、`openclaw gateway restart`。验证：高并发会话下不再出现 undefined storePath 异常。风险：如果磁盘权限/路径本身错误，升级后仍会失败。
GITHUBDiscovered 2026-02-15Author maxx-ca
Prerequisites
- Your environment can be upgraded to a build that includes PR #14755.
- You have access to gateway logs and can run a concurrent-session smoke test.
Steps
- Confirm current version and note whether lock/storePath errors are present in recent logs.
- Upgrade to a version that includes PR #14755, then restart gateway cleanly.
- Replay the same concurrent session workload (parallel chats/tools) that previously triggered the issue.
- Check logs for lock behavior and confirm no `undefined storePath` exception appears.
Commands
openclaw gateway statusopenclaw gateway restartopenclaw statusVerify
Under repeated concurrent tests, sessions complete normally and no storePath-undefined lock crash is logged.
Caveats
- This fix guards one failure mode; filesystem permission/path misconfiguration can still break session persistence（需验证）.
- Always validate on staging first when lock behavior changes in production workloads.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗