Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

fix(performance): go-faster Step 1 reports no Python when the Bash tool runs zsh

已关闭
#6,336 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@kyle-sexton 已经在做这个了。

开始于 2026年10月11日。

  • #7074 来自 @kyle-sexton —— 未关闭

评估

难度
3/5
预计耗时
半天
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
bash, python, shell, zsh

调研方向

Start at plugins/performance/skills/go-faster/SKILL.md around the preamble that sources harness-lib.sh, then plugins/performance/scripts/harness-lib.sh harness_require_python (type -P). Make that lookup portable or wrap the preamble in bash -c, and scan other harness-lib.sh callers. Point the go-faster-sweeper at scripts/harness-lib.sh not lib/. Done when the preamble resolves python3 from a zsh Bash-tool shell and a stay-quiet test covers that.

由索引模型根据 Issue 内容生成。

描述

good first issue needs-triage priority: medium

Problem

/performance:go-faster Step 1 reports PY=unresolved ("no python3 or python on PATH runs") on a host where python3 runs, when the Bash tool's shell is zsh. The skill then stops.

The preamble at plugins/performance/skills/go-faster/SKILL.md:35 runs ( source "${CLAUDE_PLUGIN_ROOT}/scripts/harness-lib.sh" && harness_require_python ... ) in the Bash tool's own shell. harness_require_python (plugins/performance/scripts/harness-lib.sh:184-197) resolves each candidate with type -P, which is bash-only. zsh prints type: bad option: -P, every candidate is skipped, and the function dies.

A second defect from the same run: the dispatching session reported this to the go-faster-sweeper agent, and the sweeper could not reproduce it because it looked for harness-lib.sh in the plugin's lib/ directory. The file lives in scripts/.

Evidence

  • 2026-10-04, WSL2 host, Bash tool shell zsh: the preamble printed the HARNESS FAIL line; command -v python3 gave /home/kyle/.local/bin/python3 (3.14.7); bash -c 'source .../scripts/harness-lib.sh && harness_require_python && echo $HARNESS_PYTHON' printed that same path.
  • The sweep's report lists the finding as session-work-4, "not reproduced: harness-lib.sh is not in this plugin's lib directory".

Fix

  • Run the preamble under bash explicitly (bash -c '...'), or make harness_require_python portable (command -v plus an absolute-path check in place of type -P). Check the plugin's other harness-lib.sh callers for the same shape.
  • Point the sweeper at scripts/harness-lib.sh wherever it resolves the library.
  • A stay-quiet test: the preamble resolves Python when run from zsh.

Related

  • #6234 (go-faster from a worktree-isolated session), a different failure in the same skill.
主要语言
Shell
星标
22
派生
2
平均合并
8 小时 44 分钟
30 天内合并 PR
926

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。