Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#430 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend, cloud

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
1
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/ace2

Tutte le issue di githubnext/ace2

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.