Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Expose native patch drift and cache recovery in desktop dev builds

Aberta
  • Algo errado?
#173 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
68/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
swift, typescript
Domínio
build-system

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
1
Forks
0
Nenhum PR com merge em 30d

Preparar o ambiente

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de githubnext/ace2

Todas as issues de githubnext/ace2

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.