Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Expose native patch drift and cache recovery in desktop dev builds

Offen
  • Stimmt etwas nicht?
#173 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
68/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
swift, typescript
Bereich
build-system

Rechercherichtung

Start from the drift diagnostic in helper.ts (The native checkout differs from every pinned patch prefix...) and the wrapper stack in apps/desktop's sparkle.ts / build.ts that swallows the Electrobun exit code under Bun workspace filtering. Then inspect the root desktop command to see where filtered output hides the underlying error, and compare with bun scripts/build.ts dev --run from apps/desktop as the bypass path. Done means the failure surfaces through the root command and the drift message names the offending cache path plus the non-destructive apps/desktop/native/.build move-aside recovery, without resetting the checkout.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Observed

On main at 39191bb, bun desktop dev exits with Electrobun code 1. Bun workspace-filter output elides the underlying diagnostic and repeatedly redraws the task header, leaving only the wrapper stack in sparkle.ts / build.ts.

Read-only inspection of the failing checkout found the pinned Peekaboo HEAD (4d43dc9d80cd2aa3787a27f54b76d692db1dcf8f) with native patch drift. Replaying the build verifier with a temporary private Git index found that none of the 15 accepted states (unpatched through the complete 14-patch stack) matches the cached working tree. helper.ts consequently rejects it with: The native checkout differs from every pinned patch prefix. Resolve source drift before building. Bun 1.4.0 and Swift 6.4 meet the build requirements. No full rebuild or cache mutation was performed during diagnosis.

Needed

  • Keep the underlying build failure visible through the root desktop command rather than hiding it behind filtered output.
  • Include the offending cache path and actionable, non-destructive recovery instructions in the drift diagnostic.
  • Preserve unknown native edits; do not automatically reset or delete a mismatched checkout.

Recovery is to move apps/desktop/native/.build aside as a backup and rebuild, causing SwiftPM to recreate the pinned dependencies and Ace to apply the current patches. Invoke bun scripts/build.ts dev --run from apps/desktop to bypass the root workspace-filter elision.

Found in Ace while investigating a user-reported development-loop failure. Related: #55. Dogfooding: #5.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

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 githubnext/ace2

Alle Issues in githubnext/ace2

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

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