Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#430 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
backend, cloud

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/ace2

Alle Issues in githubnext/ace2

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.