[Bug]
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
提交前确认 · Pre-submission checklist
- 我已搜索过现有 issue，确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
- 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category
稳定性 / 崩溃 · Stability / Crash
涉及的 Agent 框架 · Agent framework
ZCode Agent（自研）
严重程度 · Severity
阻塞使用 · Blocking (无法使用核心功能 / core function unusable)
复现频率 · Reproducibility
必现 · Always
问题描述 · Description
使用 Remote 模式登录带有 NAS 共享存储的机器时，如果 home 目录和连带的 .zcode 文件夹在共享存储目录出现多台机器共写问题是会导致 SQLite 被写坏，出现"ZCode agent transport closed"。
复现步骤 · Steps to reproduce
- 打开 zcode 使用 ssh remote 连接带有 NAS 共享存储的服务器 A。
- 再次重复步骤 1，连接服务器 B。
- 出现 "ZCode agent transport closed"。
期望表现 · Expected behavior
在一个会话中使用 Zcode 同时登陆多台机器多个项目，应该可以同时访问不同 remote 机器的不同项目。
实际表现 · Actual behavior
实际导致会话崩溃。
ZCode 版本 · ZCode version
v3.9.1
设备 / 系统 / 浏览器 · Device / OS / Browser
Ubuntu + Windows
截图 / 录屏 / 日志 · Screenshots / Recordings / Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the listed Remote-mode steps with two machines sharing the home and .zcode directories, then inspect logs around the "ZCode agent transport closed" failure and SQLite writes. There are no source files or tests named; done means concurrent sessions on different remote machines remain usable without SQLite corruption or a session crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100