Uncaught exception on simple /resume

Aperta
  • Qualcosa non va?
#1,132 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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js, wasm
Ambito
cli

Direzione di ricerca

Start by tracing the /resume session selection flow into the Ink rendering path; the stack identifies ink, yoga-layout, and the getComputedWidth call as the crash point. Reproduce by selecting the last session on Windows, then inspect how the resumed session’s UI is rendered. Done means resuming a session no longer triggers the memory access out of bounds exception.

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

Descrizione

Summary

Resuming a session from the list leads to uncaught exceptions

Expected Behavior

Resume a session

Actual Behavior

✖ CRITICAL: Uncaught Exception!
This is an unexpected error. Please file a bug report at https://github.com/CommandCodeAI/command-code/issues/new
✖ ERROR → RuntimeError
ℹ REASON → memory access out of bounds
ℹ ERROR STACK ↓
RuntimeError: memory access out of bounds
at wasm://wasm/000460e2:wasm-function[215]:0xd5ef
at wasm://wasm/000460e2:wasm-function[185]:0xcf8c
at X.getComputedWidth (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:33:52)
at renderer (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/ink/build/renderer.js:32:49)
at onRender (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/ink/build/ink.js:348:56)
at debounce$1.edges.edges (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/compat/function/debounce.mjs:12:17)
at invoke (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/function/debounce.mjs:45:9)
at debounced (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/function/debounce.mjs:82:31)
at debounced (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/compat/function/debounce.mjs:26:14)
at Ink.rootNode.onRender (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/ink/build/ink.js:211:17)

ℹ Trace ID: unknown
Share this ID with support to help debug your issue.

✖ CRITICAL: Unhandled Promise Rejection!
This is an unexpected error. Please file a bug report at https://github.com/CommandCodeAI/command-code/issues/new
✖ ERROR → RuntimeError
ℹ REASON → memory access out of bounds
ℹ ERROR STACK ↓
RuntimeError: memory access out of bounds
at wasm://wasm/000460e2:wasm-function[215]:0xd5ef
at wasm://wasm/000460e2:wasm-function[185]:0xcf8c
at X.getComputedWidth (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:33:52)
at renderer (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/ink/build/renderer.js:32:49)
at onRender (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/ink/build/ink.js:348:56)
at debounce$1.edges.edges (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/compat/function/debounce.mjs:12:17)
at invoke (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/function/debounce.mjs:45:9)
at debounced.flush (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/function/debounce.mjs:74:3)
at debounced.flush (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/es-toolkit/dist/compat/function/debounce.mjs:30:14)
at settleThrottle (file:///C:/Users/ADMIN/AppData/Roaming/npm/node_modules/command-code/node_modules/ink/build/ink.js:132:24)

Loading sessions…

Steps to reproduce the issue
  1. /resume
  2. select the last session
  3. crash
Command Code Version

v1.88.5

Operating System

Windows

Terminal/IDE

vscode

Shell

No response

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

No response

Lingua principale
Nessun dato sulla lingua
Stelle
4.2k
Fork
377
Merge medio
1g 17m
PR unite (30g)
7

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 CommandCodeAI/command-code

Tutte le issue di CommandCodeAI/command-code

Issue simili

Altre issue su CLI

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.