Spec 9: world-vercel step listing stays stale for over 30s after a run completes

Aperta
#5,605 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

Start with stepsOf in packages/core/e2e/e2e.test.ts and the spec 9 README section “Steps on world-vercel”; compare world.steps.list() and workflow inspect steps with the event log after run_completed. Reproduce the affected cases named in the issue, including instanceMethodStepWorkflow and the experimental_retention: 0 run. Done when the listing converges reliably on spec 9 and the e2e assertions can use it on every lane.

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

Descrizione

On spec 9 runs against world-vercel, world.steps.list() (and workflow inspect steps) sometimes still shows a step as running or pending, or leaves it out, more than 30-60s after run_completed, even though the run's event log already holds that step's step_started and terminal event. The spec 9 README ("Steps on world-vercel") says the listing can lag the log, but this lasts much longer than a step written "moments ago", and it is what users see in the steps view.

Seen in CI on the spec 9 lanes in instanceMethodStepWorkflow (~18 times in two days), StepNotRegisteredError fails the step but workflow can catch it and step-argument serialization failure is catchable in workflow code. It also showed up as an empty inspect steps --withData listing for an experimental_retention: 0 run. Steps whose events land within ~100ms of each other seem most affected.

#5601 moved those e2e assertions onto the event log on the spec 9 lane only, so nothing in CI checks that the listing converges on spec 9. The other lanes still assert on the listing. Once the listing converges reliably, stepsOf in packages/core/e2e/e2e.test.ts can go back to the listing on every lane.

🤖 Generated with Claude Code

Lingua principale
TypeScript
Stelle
2.5k
Fork
401
Merge medio
1g 21h
PR unite (30g)
201

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 vercel/workflow

Tutte le issue di vercel/workflow

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.