zai-org / zai-org/feedback

[Bug]zcode 无法打开其它ide都可以打开的项目

Open
#48 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: Bug
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

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

严重程度 · Severity

阻塞使用 · Blocking (无法使用核心功能 / core function unusable)

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

主进程发生 JavaScript 错误
未捕获的异常:
错误:路径必须是绝对路径
at initializeCrashCapture
(file:///D:/ZCode/resources/app.asar/out/main/index.js:69:2333)
at file:///D:/ZCode/resources/app.asar/out/main/index.js:69:3585
at ModuleJob.run (node:internal/modules/esm/module_job:430:25)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async onImport.tracePromise.proto_
(node:internal/modules/esm/loader:661:26)
at async node:electron/js2c/browser_init:2:145579
at async asyncRunEntryPointWithESMLoader
(node:internal/modules/run_main:116:5)

复现步骤 · Steps to reproduce

无法打开zcode

期望表现 · Expected behavior

主进程发生 JavaScript 错误
未捕获的异常:
错误:路径必须是绝对路径
at initializeCrashCapture
(file:///D:/ZCode/resources/app.asar/out/main/index.js:69:2333)
at file:///D:/ZCode/resources/app.asar/out/main/index.js:69:3585
at ModuleJob.run (node:internal/modules/esm/module_job:430:25)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async onImport.tracePromise.proto_
(node:internal/modules/esm/loader:661:26)
at async node:electron/js2c/browser_init:2:145579
at async asyncRunEntryPointWithESMLoader
(node:internal/modules/run_main:116:5)

实际表现 · Actual behavior

无法打开zcode

ZCode 版本 · ZCode version

所有这几天的版本

设备 / 系统 / 浏览器 · Device / OS / Browser

windows 对接 wsl环境

截图 / 录屏 / 日志 · Screenshots / Recordings / Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the launch failure on Windows with a WSL environment and inspect the initializeCrashCapture stack location reported in out/main/index.js. Compare behavior across the affected recent versions and verify that ZCode opens the project successfully without the absolute-path error.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript, node.js
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.