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

[ci-scan-feedback] Recency-sorted stem search to close open-sibling KBE dedup gap

Aperta Adatta ai principianti
  • Qualcosa non va?
#134,589 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, markdown
Ambito
ci-cd

Direzione di ricerca

Leggi .github/workflows/shared/create-kbe.instructions.md, in particolare la variazione 6 alle righe 69-75, e controlla come viene descritta la ricerca esistente dello stem con la corrispondenza migliore. Aggiorna le istruzioni in modo che lo scanner controlli anche gli ultimi 10 risultati circa con lo stesso stem, ordinati per data di creazione. Il lavoro è completo quando la successiva esecuzione dello scanner può far emergere un sibling recente e aperto senza modificare la classificazione, la struttura JSON o la specificità della firma.

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

Descrizione

agentic-workflows area-Infrastructure untriaged

Triggering signals

  • KPI tracker #128742 (rubric finding) — the wasm JIT/opt/GuardedDevirtualization/badinlinee signature was re-filed three times in 48h while a predecessor stayed open: #134169 (open 2026-09-18→09-20), then #134292 and #134302 both filed 2026-09-20 with an identical ErrorMessage ("Failed test: JIT/opt/GuardedDevirtualization/badinlinee/badinlinee.cmd"). All three closed completed, so this open-dedup miss never registers in the wrong-closure rate, yet it is a direct driver of the New-KBE burst signal (peak day 8 on 09-20). https://github.com/dotnet/runtime/issues/134292 https://github.com/dotnet/runtime/issues/134302
  • Same pattern recurs on other stems (MsQuic expected-error handshake timeout #134171 → dup of #133645), all closed as automated area-owner dedup with 0 maintainer rejection comments and 0 mis-attributions — the recall gap, not classification, is the fixable defect.

Proposed edits

  • .github/workflows/shared/create-kbe.instructions.md:69-75 (variation 6, "Search for an existing KBE") — after the best-match stem search, re-issue the same stem search sorted created descending and scan the newest ~10 results, so an open same-stem KBE filed by the immediately preceding twice-daily sweep surfaces deterministically instead of being ranked past the first page. Rationale ties directly to the badinlinee triple-refile above.

Expected behavior change

The next scanner run's existing-KBE search will surface a same-stem open sibling that a prior sweep filed only hours earlier, even when GitHub best-match relevance would bury it past the first page of results. This closes the open-dedup miss that let one wasm test signature spawn three separate [ci-scan] KBEs in two days — reducing both duplicate/completed-closed re-files and their contribution to the New-KBE burst outage signal, without touching classification, JSON shape, or signature specificity.

[!NOTE]
This PR description was generated by GitHub Copilot (ci-failure-scan-feedback workflow).

Generated by CI Outer-Loop Failure Scanner — Feedback · opus48 · 687 AIC · ⌖ 18.3 AIC · ⊞ 18.2K · ◷

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Original error: The process '/usr/bin/git' failed with exit code 1

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

To create a pull request with the changes:

# Download the artifact from the workflow run
gh run download 36002458532 -n agent -D /tmp/agent-36002458532

# Fetch the bundle into a temporary ref, then update the local branch
git fetch /tmp/agent-36002458532/aw-ci-scan-feedback-recency-sorted-stem-dedup.bundle refs/heads/ci-scan-feedback/recency-sorted-stem-dedup:refs/bundles/create-pr-ci-scan-feedback-recency-sorted-stem-dedup-61416dbd81bf4ff1-7c3d4a9b
git update-ref refs/heads/ci-scan-feedback/recency-sorted-stem-dedup-61416dbd81bf4ff1 refs/bundles/create-pr-ci-scan-feedback-recency-sorted-stem-dedup-61416dbd81bf4ff1-7c3d4a9b
git checkout ci-scan-feedback/recency-sorted-stem-dedup-61416dbd81bf4ff1
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d refs/bundles/create-pr-ci-scan-feedback-recency-sorted-stem-dedup-61416dbd81bf4ff1-7c3d4a9b

# Push the branch to origin
git push origin ci-scan-feedback/recency-sorted-stem-dedup-61416dbd81bf4ff1

# Create the pull request
gh pr create --title '[ci-scan-feedback] Recency-sorted stem search to close open-sibling KBE dedup gap' --base main --head ci-scan-feedback/recency-sorted-stem-dedup-61416dbd81bf4ff1 --repo dotnet/runtime
Lingua principale
C#
Stelle
18.3k
Fork
5.6k
Merge medio
2g 22h
PR unite (30g)
614

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 dotnet/runtime

Tutte le issue di dotnet/runtime

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.