CircleCI-Public / CircleCI-Public/python-orb
3.2.0 breaks caching system due to `circleci` lacking the `env` subcommand
- Lenguaje dominante
- Shell
- Estrellas
- 15
- Forks
- 41
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
## Orb version:
3.2.0 (specifically as of the commits from #131) - can confirm dropping back to 3.1.0 avoids the issue
## What happened:
`circleci local execute name-of-job` results in:
```
Error: unknown command "env" for "circleci"
Run 'circleci --help' for usage.
ERRO[0000] Exit with status 1 due to generic error error="unknown command \"env\" for \"circleci\""
```
stemming from an internal script (the one for linking lockfiles) calling out to `circleci env subst`.
I wasn't able to determine exactly where this ends up running; or rather, why the `circleci` it calls is neither visible in eg `docker run --rm -it cimg/python:3.8` (for any tags, eg behavior is same under `cimg/python:3.13`) nor matching the version in my localhost's environment (which is the latest possible `circleci` and does have `circleci env subst`).
I also haven't progressed to pushing my CI config updates to the server so I'm not sure if this issue occurs outside of `circleci local`.
## Expected behavior:
Expected to actually run my task locally, as happens correctly with orb 3.1.0 and below, usually leading to errors that are actually my fault 😂
## Additional Information:
Not super likely to matter but my execution environment is Arch Linux pinned to a 2024-ish archive repo. my `circleci` CLI version is `0.1.32638+2bfc35c (release)`.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Comienza con el script interno de enlace de lockfiles mencionado en el informe y rastrea dónde `circleci local execute` invoca `circleci env subst`. Compara el comportamiento entre orb 3.2.0 y 3.1.0 y, después, verifica que la ejecución local indicada se complete después de este comando sin el error de subcomando desconocido.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- shell
- Área
- ci-cd
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 35/100