Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Expose native patch drift and cache recovery in desktop dev builds

Ouverte
  • Quelque chose ne va pas ?
#173 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
68/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
swift, typescript
Domaine
build-system

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1
Forks
0
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/ace2

Toutes les issues de githubnext/ace2

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.