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

[Labs] Add a lab details API and lab filters on existing read endpoints

Aperta
  • Qualcosa non va?
#2,169 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
24/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python, sql
Ambito
api, backend, database

Direzione di ricerca

Start with the existing lab listing query, which defines the expected build, boot and test counts for one lab. The new details read joins labs on builds.lab_id and tests.lab_id and must not read the JSON lab fields in misc. The existing test.lab filter currently runs in Python after rows load; move it into SQL and keep its behaviour. Done when the counts match the listing row and query plans are checked.

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

Descrizione

Backend q4-plan
Lab details

Add a read endpoint for one lab, keyed by labs.name, with the same origin and interval as the listing.

The response must match that lab's listing row (build, boot, and test status counts) and include the breakdown behind it: trees and hardware that contributed, with their status counts. An unknown lab, or a lab with no rows in the window, returns an empty result rather than an error.

Read labs through builds.lab_id and tests.lab_id. Do not add a misc->>'lab' or misc->>'runtime' fallback on this endpoint.

Lab filter on other views

Accept a lab on the tree, hardware, and issue read endpoints and apply it in the query, on both builds and tests. Rows with lab_id NULL do not match.

The existing test.lab filter runs in Python after the rows are loaded. Move that exclusion into SQL. Callers that already send test.lab should keep working.

Acceptance criteria

  • GET one lab by name, with origin and interval, returns build, boot, and test counts consistent with that lab's listing row, plus the trees and hardware behind those counts.
  • The details query joins labs on lab_id and does not read the JSON lab fields.
  • Tree, hardware, and issue reads accept a lab and filter builds and tests in SQL.
  • An existing test.lab request still filters, without loading the unfiltered window first.
  • Query plans for the details endpoint and the filtered reads are checked. A new index is added only if the current lab_id indexes are not enough.
  • No dashboard UI.
Lingua principale
Python
Stelle
10
Fork
32
Merge medio
4g 12h
PR unite (30g)
23

Preparare l'ambiente

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 kernelci/dashboard

Tutte le issue di kernelci/dashboard

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.