zai-org / zai-org/feedback

[Bug] unable to get local issuer certificate

Open
#14 3 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

稳定性 / 崩溃 · Stability / Crash

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

严重程度 · Severity

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

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

有包年订阅,在cc通过api使用正常。在zcode中发送任意消息报错,unable to get local issuer certificate。

Image

ZCode 报错信息

报错摘要
unable to get local issuer certificate

TraceID: 8966ebc6-de0a-45b8-9d56-049583b672c2

报错详情
Turn execution failed
provider=builtin:bigmodel-coding-plan provider_code=UNABLE_TO_GET_ISSUER_CERT_LOCALLY model=GLM-5.2 request=7f6b083c-8aa6-4ae6-b5ce-0f13a00937cf reason=unknown retryable=false

复现步骤 · Steps to reproduce
  1. 打开zcode
  2. 发送任意消息
期望表现 · Expected behavior

能够正常对话

实际表现 · Actual behavior

一直报错,无法使用

ZCode 版本 · ZCode version

v3.1.0。 上个版本也一样

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

Macbook pro m1

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

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 failure on a MacBook Pro M1 with ZCode v3.1.0, using the reported steps and the error details in this issue. Investigate the certificate error and verify the fix by sending a message successfully without the issuer-certificate failure.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.