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

Keep items with open runs on the board beyond the 500-item window

Chiusa
  • Qualcosa non va?
#719 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #761 di @usine-phildl — integrata

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

Start with Operator.projectOverview, Operator.task, and ItemProjectionReader.list, then read docs/adr/0024-tasks-project-linked-items.md for the board-window contract. Trace how open runs are combined with item projections and how linked-task grouping uses the selected items. Add a regression test with more than 500 stored items and verify the older item's card remains available on the board and for task detail and board moves, while historical reads remain bounded.

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

Descrizione

bug

The board omits older items with open runs once 500 higher-numbered items have stored projections. Updating labels does not make those items visible.

Operator.projectOverview calls ItemProjectionReader.list with OVERVIEW_BOARD_ITEMS = 500. The reader orders by descending itemNumber, not by activity, and applies the limit before task grouping. The overview reads open runs separately but never adds their missing item projections to the board input. Operator.task uses the same board window (ADR 0024).

This explains the number-dependent pattern in #702: #182 and #195 had waiting start-dev runs and ready-for-agent, while #689, #692, and #696 had cards. The repository has over 500 higher-numbered issues and pull requests. This diagnosis comes from the query and projection code; the incident's live database was not inspected.

Reproduction: store an open issue with a waiting run, then store 500 higher-numbered items. The old issue remains available through ItemProjectionReader.get, but the board contains none of its items. Changing its labels does not change the result.

Done when:

  • Items with open runs remain on the board even outside the 500-item history window.
  • Task detail and board moves can access those cards using the same item selection.
  • Bounded historical reads and linked-task grouping remain consistent.
  • A regression test uses more than 500 stored items and verifies a waiting run's item remains visible.

Related: #702 restores item identity on approval needs independently of board membership. See docs/adr/0024-tasks-project-linked-items.md for the board-window contract.

— usine agent: developer

Lingua principale
TypeScript
Stelle
1
Fork
0
Merge medio
4h 26m
PR unite (30g)
280

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 basaltbytes/usine

Tutte le issue di basaltbytes/usine

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.