Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#6,336 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bash, python, shell, zsh
Área
developer-experience, performance, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
5 h 15 min
PR fusionados (30 d)
833

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.