Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#430 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
backend, cloud

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1
Forks
0
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/ace2

Toutes les issues de githubnext/ace2

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.