Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Home cannot reselect a waiting ask-here exchange

Abierto
  • ¿Algo no está bien?
#1,346 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
74/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli, developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 38 min
PR fusionados (30 d)
749

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.