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

Keep a cloud channel's listing in step with its compute service

Aberta
  • Algo errado?
#430 0 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
25/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
backend, cloud

Direção de pesquisa

Start with the INACTIVITY threshold in services/compute/index.ts, then the Start compute and Stop compute handlers and the stopped flag in apps/host/src/compute.ts, to see how the host's record diverges from the service's state. Read docs/architecture.md (Cloud compute (beta)) for how busy and name reach the listing. Done means the listing and menu match the service after an inactivity stop, and busy and the current name show for cloud channels, verified on a deployed channel. Checkpointing (#413) is out of scope.

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

Descrição

Follow-up to #216 and #428. A cloud channel's listing is set only by what this host itself does, so it drifts from the compute service.

  • Inactivity stop: services/compute stops a container after 6 hours without activity (INACTIVITY in services/compute/index.ts). The host's stopped flag changes only on its own Start compute and Stop compute (apps/host/src/compute.ts), so that channel still lists as running. Its menu offers only Stop compute, and Start compute on a running record fails with the service's "already running" error. Records created before #428 also list as running until their next start or stop.
  • Busy and name: busy and rename projections reach the listing over the workspace link, and a compute record has none. The listing shows a cloud channel idle under its created name until the channel's own metadata is read (docs/architecture.md, Cloud compute (beta)).

Remaining

  • Reflect the service's actual running/stopped state, including an inactivity stop, in the record and listing, and offer the action that applies.
  • Carry busy and the current name into the listing for cloud channels.
  • Verify against the deployed service with a channel that the service stops for inactivity.

The inactivity stop doesn't checkpoint, so work since the last checkpoint is lost; that durability gap is #413. This issue only covers what the listing shows.

Tracked by #58.

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.