Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Expose native patch drift and cache recovery in desktop dev builds

Open
  • Is something wrong?
#173 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
swift, typescript
Domain
build-system

Research direction

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.

Written by the indexing model from the issue text.

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.

Dominant language
TypeScript
Stars
1
Forks
0
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/ace2

All issues in githubnext/ace2

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.