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

Home cannot reselect a waiting ask-here exchange

Aperta
  • Qualcosa non va?
#1,346 1 commento 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
74/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli, developer-experience

Direzione di ricerca

Start with the focused gate TestTUIE2E/ask_here_end_to_end, then trace app.homeKey and homeView.move in internal/tui3/home.go, followed by homeView.gridMove and columnStops in homegrid.go and homeView.exchangeLines in homeexchange.go. Compare keyboard and mouse selection behavior for a visible ? waiting on you row. Done means the unit and e2e checks pass, Enter reopens the card with keyboard ownership, and the manual pages and change entry describe the behavior.

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

Descrizione

area:chat bug sev:serious

What happened

REGRESSION seen on commit 17ae56d34 (staging-20260921-17ae56d3496f) on 2026-09-21. Lane C, ask_here_end_to_end, left this waiting exchange on Home:

? remind me in 1 minute to drink wat…  ? waiting on you

The test then could not put the cursor back on the exchange row; Up skipped it, so Enter could not reopen its ask-here card. On v0.3.0 (9258f7052), enter on the row gave the pane the keyboard, with the card on it.

The behavior is likely related to docs/changes/unreleased/1071-approvals-wheel.md, whose selection-ownership work changed Home navigation.

Replication

Deterministic (no model).

No no-model reproduction is established. Run the focused repository gate:

go test -tags e2e -count=1 -v ./internal/e2e -run '^TestTUIE2E/ask_here_end_to_end$'

Today it exits nonzero with could not put the cursor back on the exchange row after creating the visible ? waiting on you row.

Field (real models).

Set OPENROUTER_API_KEY and run the same command; allow about two minutes and less than $0.03. It creates an ask-here exchange, moves away on Home, presses Up to return, and presses Enter. The v0.3.0 run is the control.

Where

The relevant selection and rendering seams are app.homeKey and homeView.move in internal/tui3/home.go, homeView.gridMove and columnStops in internal/tui3/homegrid.go, and homeView.exchangeLines in internal/tui3/homeexchange.go. The evidence does not identify a specific faulty branch.

The fix

Keyboard navigation on Home must include a waiting ask-here exchange as one selectable row. Pressing Enter on that row must reopen its card and give the pane the keyboard, regardless of whether mouse navigation happened earlier.

Acceptance

  • e2e: Through TestTUIE2E/ask_here_end_to_end in tmux, press Up onto the row whose state is ? waiting on you, press Enter, assert the ask-here card is visible and owns keyboard input, and exit 0.
  • e2e: Through the same Home screen, alternate mouse hover and keyboard Up; assert the keyboard-selected exchange is the only selected row and Enter opens that row.
  • Unit: columnStops and homeView.gridMove include each actionable ? waiting on you exchange exactly once in keyboard order.
  • The manual pages internal/manual/chat/asking-from-home.md and internal/manual/chat/home.md describe reopening with Enter, and the change entry's invalidates names the old belief that waiting exchange rows were not keyboard stops.

Filed from the 2026-09-21 staging verification of 17ae56d34; the lane reports, frames and e2e logs are in the owner's handoff folder for this promotion.

Lingua principale
Go
Stelle
115
Fork
14
Merge medio
9h 35m
PR unite (30g)
752

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. 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 Agent-Field/CodeAF

Tutte le issue di Agent-Field/CodeAF

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.