github / github/spec-kit

[Bug] Windows Codex PATH can crash HTTPS updates with OPENSSL_Applink

Aperta
#4,433 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub
author-awaiting author-needs-info author-needs-proof bug-assess severity-medium triage-can-wait
Lingua principale
Python
Stelle
137k
Fork
12.3k
Merge medio
2g 12h
PR unite (30g)
159

Descrizione

### Spec Kit version

`specify 1.0.4`, installed as a uv tool on Windows.

### Environment

- Codex Desktop local task on Windows
- The task PATH prepends Codex-owned native dependency directories, including Poppler and Git directories that contain their own `libssl-3-x64.dll` and `libcrypto-3-x64.dll`.
- `specify.exe` is the uv-installed launcher under `%USERPROFILE%\.local\bin`.

### Reproduction

From an initialized consumer with registered HTTPS catalogs, run either:

```powershell
specify workflow update program-kit-bootstrap
specify bundle update program-kit --integration codex
```

Both commands reproducibly exit 1 before completing the remote update with:

```text
OPENSSL_Uplink(...): no OPENSSL_Applink
```

The failure occurs specifically in the Codex Desktop process environment. A local/offline component installation can proceed because it does not enter the failing HTTPS path.

### Expected behavior

Spec Kit HTTPS/catalog operations should use the OpenSSL runtime packaged with its Python environment and must not load an ABI-incompatible DLL merely because another application prepended native tools to PATH. If the launcher cannot isolate its DLL search path, it should fail with an actionable dependency diagnostic rather than the OpenSSL applink abort.

### Impact

Documented `workflow update` and `bundle update` commands cannot run from Codex Desktop on affected Windows hosts. This blocks unattended governed upgrades and encourages consumers to use incomplete local recovery sequences.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Riproduci `specify workflow update program-kit-bootstrap` e `specify bundle update program-kit --integration codex` nell’ambiente Codex Desktop Windows. Esamina come il launcher `specify.exe` installato con uv e il relativo percorso HTTPS Python risolvono le DLL di OpenSSL quando Codex antepone directory native a PATH. Il lavoro è completato quando entrambi gli aggiornamenti HTTPS terminano correttamente, oppure quando una diagnosi delle dipendenze utilizzabile sostituisce l’OpenSSL applink abort.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
python
Ambito
cli, devtools, operating-systems
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Attiva
Chiarezza
Abbastanza chiara
Idoneità per principianti
48/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.