Windows contributor DX: bun run check, setup and release:test fail on Windows

Offen
#260 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
bash, bun, github-actions, python, rust, shell

Rechercherichtung

The first stop is package.json: every script that calls scripts/*.sh directly needs a bash prefix (the failing one is check → scripts/check-skills.sh), and the TS release tests that spawn a script need the same prefix. Then read setup.sh for the Linux hints and add a MINGW/MSYS branch covering MSVC Build Tools, WebView2, Git Bash and actionlint/zizmor, plus a Windows section in docs/contributing.md. Add a Windows CI job running bun run check without Rust; done means a fresh Windows 11 machine gets rc=0 from bun run setup through bun run check.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area: ci priority: 2 normal status: confirmed type: chore

Observed on one Windows 11 machine (Git Bash, Bun, WSL installed) while gating #259 (gate note: https://github.com/codeatlasdev/atlas/pull/259#issuecomment-6882316955). The release:test failures also happen on main, so they are a pre-existing Windows break, not caused by #259. Causes marked "inferred" were not traced to Bun source.

Contributors on Windows cannot run the repo's own gate today. Found while gating #259 on Windows 11 (Git Bash + Bun):

What breaks

  • bun run check stops after cargo-deny: scripts/check-skills.sh fails with bun: unknown error. Inferred: Bun's script runner on Windows does not execute a .sh file by path (observed: bun: unknown error and EFTYPE uv_spawn). Same for every script that calls scripts/*.sh directly: setup, desktop:dev, desktop:build, lint:workflows, mobile:check, release:*, sweep, icons:dev.
  • release:test: 38 failures with EFTYPE: inappropriate file type or format, uv_spawn, identical on main: the TS tests Bun.spawnSync([script]) on .sh helpers; python3 is not the Windows name (python/py).
  • lint:workflows: actionlint/zizmor not installed and setup.sh does not say how on Windows.
  • setup.sh has hints for Linux packages only; nothing for Windows (WebView2, MSVC Build Tools, cargo-xwin not needed locally, etc.).
  • CI job rust-windows builds and tests Rust, but no CI job runs the scripts or bun run check on Windows, so this regresses silently.

Works by hand: bash scripts/check-skills.sh, bun run desktop:check (3199 tests), Rust fmt/clippy/nextest (1920 tests).

Proposal

  1. Every package.json script runs shell scripts as bash scripts/x.sh (Git Bash is already required for the repo); TS tests spawn ["bash", script]; Python via python3 || python.
  2. setup.sh detects Windows (uname -s MINGW/MSYS) and checks/hints: MSVC Build Tools, WebView2 runtime, Git Bash, cargo nextest, cargo deny, actionlint + zizmor via winget/scoop.
  3. docs/contributing.md: a "Windows" section (prereqs, bun run desktop:dev, what is macOS-only: agent instances, Lab, mirror).
  4. CI: a Windows job running bun run check minus the Rust part (already covered), so script breakage on Windows turns CI red.
  5. Optional later: port the most used scripts (setup, check-changed, heavy) to Bun TS so they need no bash at all.

Done when

A fresh Windows 11 machine with Git, Rust, Bun goes bun run setup → bun run check → rc=0, and CI enforces it.

Vorherrschende Sprache
Rust
Sterne
3
Forks
1
Ø Merge
9 Std. 51 Min.
Gemergte PRs (30 T.)
310

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codeatlasdev/atlas

Alle Issues in codeatlasdev/atlas

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.