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

A stopped workflow stage should show its child stages as stopped too

Fermée
  • Quelque chose ne va pas ?
#646 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@lavaman131 y travaille déjà.

Depuis le 16/10/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

When a workflow run stops, its run card in Chat shows the stopped stage as stopped, but the stages under it keep their last status, such as running or queued. The card then reads as though work is still going on inside a run that has ended.

Steps to reproduce

  1. Start a workflow run from a document's Planner whose stages have child stages, for example a stage that fans out into several sub-stages.
  2. While a parent stage and its children are running, stop the run. Ending the Planner's connection or deleting the document also stops it.
  3. Look at the run card in Chat (apps/web/src/chat/run-card.tsx).

Expected: every stage under a stopped stage shows stopped too, or a muted "not run" for ones that never started. The tree should agree with its parent, and no spinner should keep going under a stopped stage.

Actual: the parent shows stopped, while its children still show running or queued, sometimes with an active spinner.

Suggested fix

  • When the card renders a stage whose status is stopped, failed or cancelled, show each descendant that hasn't reached its own end state as stopped. A descendant that already finished (done or failed) keeps its own status.
  • Do this where the card builds its stage tree from the Planner's run report, so it applies however the report arrived (live update or reload). Optionally apply the same rule where the server stores the report (packages/protocol/chat.d.ts).
  • Add a unit test: a stopped parent with running, queued and done children renders stopped, stopped and done.
  • Add a design-audit plate: extend design-audit/plates/workflow-runs.tsx with a stopped run that has nested stages.

Assistant-workflow: inline
Assistant-duration: unmeasured
Assistant-verification: manual unavailable: UX feedback from lavaman131 after a run stopped mid-stage on the hosted instance; not reproduced locally
Co-authored-by: lavaman131

Langage dominant
TypeScript
Étoiles
409
Forks
24
Merge moyen
11 h 58 min
PR mergées (30 j)
456

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun 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/chopin

Toutes les issues de githubnext/chopin

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.