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

Dev diagnostics: ABANDONED_FLIGHTS fires on streamed frame slot args that supersede by design

Aperta
  • Qualcosa non va?
#3,852 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, typescript
Ambito
devtools

Direzione di ricerca

The false positive originates in the per-slot async-arg memo in packages/web/frames/src/client.ts where createMemo(() => args()[key]) causes streamed frames to supersede their own flights. Start by examining how abandonedFlights is counted in the dev diagnostics and whether the check can distinguish intentional supersession from churn. The fix will likely involve exempting or annotating these cases in the diagnostic output.

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

Descrizione

Split out of #3739, where it was reported as an aside.

examples/chat, running under vite-plugin-solid's dev server with the performance tracks on, logs repeated ABANDONED_FLIGHTS while a reply streams:

"computed" abandoned 3 flights in 1000ms
<App> › <For> › <Loading> › children › <Reply> › computed › computed

#3739 asked whether this is the HMR plumbing blind spot. It isn't, and the fix for #3739 (#3850) doesn't change it:

  • The warned node is a named computed. Plumbing nodes have no name, and the check already skips them.
  • abandonedFlights isn't one of the cost checks that checks: false turns off, so it stays on under the performance-tracks hold.
  • <Reply> is a local dynamic(() => reply(...)) server component, not an HMR-wrapped component.

The likely source is the per-slot async-arg memo in packages/web/frames/src/client.ts (createMemo(() => args()[key])). Each streamed frame starts a new flight before the previous one lands, which is supersession by design. The check has no way to tell that apart from accidental churn. This has been traced from the code only; examples/chat hasn't been run to confirm it.

The question is how ABANDONED_FLIGHTS should treat sources that supersede their own flights by design, such as streamed slot args: exempt them, mark them, or calibrate the threshold differently for them.

Lingua principale
TypeScript
Stelle
36.1k
Fork
1.1k
Merge medio
13h 13m
PR unite (30g)
306

Preparare l'ambiente

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 solidjs/solid

Tutte le issue di solidjs/solid

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.