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

Verify native development and recovery end to end in Ace

Aberta
  • Algo errado?
#55 2 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
git, shell, typescript
Domínio
release, testing

Direção de pesquisa

Start from the review-evidence comment on issue #5 and the acceptance list here; the entry points are Ace's lanes, Diff view, shell/git/gh access, and the existing release/canary commands. Pick one representative change and drive it end to end, then exercise compaction, worker/helper restart, and a development failure against a separately installed Ace plus an existing-channel backup. Done means a recorded run (channel/lane, revision, build/model, outcomes, external-tool escapes) and any observed defects filed as issues.

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

Descrição

Ace already has native coding tools, lanes, shell/Git/gh access, diffs, durable recovery, and release commands. Qualify the complete development loop so dogfooding MVP is based on working behavior rather than a feature checklist.

Acceptance

  • Complete a representative Ace change from issue and lane through edits, required real checks, Ace Diff review, PR/CI, and signed canary delivery using Ace's surfaces and native harness.
  • Verify the UI change with channel-owned browser and native tools; preserve the evidence. Follow up on any failing CI or review feedback inside Ace.
  • Continue existing work through compaction, worker/helper restart, and a development failure without lost history, unintended side-effect replay, or duplicate lane writers.
  • Keep a working installed Ace separate from the source build under development. Validate any stored-format change against an existing-channel backup; never reset the store.
  • Record the channel/lane, revision, build/model, outcomes, and any remaining external-tool escape. File observed defects as issues.

This validates existing mechanisms; it does not request another release platform. Shell git, gh, builds, and existing release commands inside Ace count. Human OS/login handoffs are legitimate. #39 owns published-upgrade qualification on another Mac; external-harness continuation (#9), host migration (#49), and mobile are separate promises.

Dogfooding MVP: #5. Depends on the required native/browser verification paths. Review evidence.

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.