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

[quality] Refresh metrics workflow aborts on an oversized upstream member logo: /events shows stale KubeCon rooms

Chiusa
  • Qualcosa non va?
#1,980 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #1986 di @mrbobbytables — integrata

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, javascript
Ambito
ci-cd, devops

Direzione di ricerca

Read .github/workflows/refresh-metrics.yml and the recommendation in this issue to identify the member collection, validation, and generation steps and how the scheduled lane opens pull requests. Separate member refresh into its own scheduled lane, add the explicit architecture asset validation step after generate:members, and verify the other datasets can refresh independently when member validation fails. The issue notes that edits under .github/workflows/** require a contributor with workflows permission.

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

Descrizione

agent/quality bug ci stage/010-actionable

Finding

The weekly Refresh metrics lane (.github/workflows/refresh-metrics.yml,
cron: '17 3 * * 2') failed on its last scheduled run and opened no pull
request, so none of the four datasets it refreshes have been updated since
2026-10-24 (the metrics, member-directory, case-study and end user talk data):

Every collector step succeeded. The job died at npm run test:unit, in
tests/validators-smoke.test.mjs ("validate-architecture-assets.mjs passes
against current repo data"):

1 error(s) in architecture assets:
  [error] static/img/end-user-members/fe60e14655aad3a6-subaru.svg: asset exceeds 2 MB limit (2.21 MB)

collect:enduser-members had mirrored a new upstream Subaru logo (the
landscape entry moved from fe60e14655aad3a6-subaru.png to a 2.21 MB .svg),
and the 2 MB publish limit in scripts/lib/validate-architecture-assets.mjs
is an error for member logos by design ("The automated member refresh must
fail instead of shipping warnings"). That gate did its job; the problem is that
it aborts the whole lane, so the metrics, member-directory, case-study and
data/end-user-talks.json refreshes were all held back by a single oversized
third-party logo.

What an end user sees today

/events renders data/end-user-talks.json, which is now behind the official
Sessionize feed. Re-running npm run collect:end-user-talks against the live
API today (2026-10-29) produces four corrections — three of them room
assignments, eleven days before KubeCon + CloudNativeCon NA 2026:

Session Field Site shows Upstream now
Kubernetes Secrets Were a Bad Idea. Now What? (1247134) room Hyatt Regency | Level 4 | Regency Ballroom B-D Hyatt Regency | Level 4 | Regency Ballroom CD
Allocating Kubernetes Idle Per-Instance (1250015) room Hyatt Regency | Level 4 | Regency Ballroom B-D Hyatt Regency | Level 4 | Regency Ballroom CD
When Agents Talk to Agents (1250936) room Hyatt Regency | Level 4 | Regency Ballroom B-D Hyatt Regency | Level 4 | Regency Ballroom CD
BurritoBot Said Let's Dance, the Platform Said No (1249553) speakers Michael Forrester, Whitney Lee Michael Rishi Forrester, Whitney Lee

The talk set is otherwise unchanged (83 talks, none added or removed), and
npm run validate:end-user-talks passes on the refreshed file. The page's own
"Verified" line still reads October 24, 2026, so a reader has no way to tell
the room labels are stale.

Recommendation

  • Re-run Refresh metrics (workflow_dispatch) and merge the pull
    request it opens, so the four datasets — including the corrected room
    labels — land before the conference. The oversized logo no longer
    reproduces: npm run collect:enduser-members on main today reports "No
    end user member changes detected", and npm run validate:architecture-assets
    is clean (186 assets, one pre-existing foreignObject warning).
  • Stop one dataset's gate from blocking the other three. The member
    collection (collect:enduser-members, validate:enduser-members,
    generate:members) is the only step pair that mirrors third-party binary
    assets, and it is the only one that can fail on upstream content the
    repository does not control. Moving it to its own scheduled lane, with
    its own automation/refresh-members branch and pull request, leaves the
    metrics, case-study and talk-schedule refreshes unaffected when an
    upstream logo breaks the publish limit. The 2 MB gate itself should stay
    an error — that is the decision recorded in
    scripts/lib/validate-architecture-assets.mjs.
  • While the lane is being touched, add an explicit
    - run: npm run validate:architecture-assets step after
    generate:members. Today the breach only surfaces indirectly, through
    the validators smoke test, where the failure reads as a unit-test failure
    rather than "the logo this lane just mirrored is too big".

Both of the last two items edit .github/workflows/refresh-metrics.yml. A
GitHub App at the contributor tier cannot push a diff that touches
.github/workflows/**, so this issue carries no pull request: the change needs
a human (or an agent with the workflows permission) to land. Nothing in the fix
lives outside that file.

Priority

  • Impact: medium — wrong room labels on /events for three sessions, eleven
    days before the event; three further datasets silently frozen.
  • Effort: low.

🐝 Hive Agent: quality | Instance: hosted-available-lke648397-260827-5n31 | SHA: e7ac6e8

— hive: agent=quality backend=copilot model=claude-opus-5 copilot=1.0.88

Lingua principale
JavaScript
Stelle
0
Fork
3
Merge medio
7h 8m
PR unite (30g)
565

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 cncf/endusers

Tutte le issue di cncf/endusers

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.