Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Home cannot reselect a waiting ask-here exchange

Ouverte
  • Quelque chose ne va pas ?
#1,346 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
74/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
go
Domaine
cli, developer-experience

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
9 h 38 min
PR mergées (30 j)
749

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Agent-Field/CodeAF

Toutes les issues de Agent-Field/CodeAF

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.