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

roadmap/labels/yaml gates: residuals ledger after the six-round critic loop (#1226) — one P2 (privacy classifier fails open) closed in round 7; 8 ranked residuals

Aperta
  • Qualcosa non va?
#1,230 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
bash, github-actions, yaml
Ambito
ci-cd, security

Direzione di ricerca

Start with roadmap_check.sh and the [99zb] gate, then read the caller paths and the daily issue-triage.yml workflow; docs/CI.md records the stated boundary. Reproduce the ranked residuals using the mentioned fixtures and existing selftest pin. Done means the selected residuals have agreed fixes, accurate receipts or diagnostics, and regression coverage without reopening the pinned exclusions.

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

Descrizione

area:gates found-by:critic kind:gate-defect

Residuals ledger for the front-door gates after the six-round blind-critic loop on PR #1226 (m1b-front-doors, head 93ff029). Final verdicts: Fable PASS / dry / fit to merge; Astra FAIL on one P2 (item 1 below) which both critics found and which is closed in the past-cap round 7 of #1226. Reproducers live under /tmp/critic-fable-c-r6/ and /tmp/critic-astra-c-r6/ on the dev box.

Class the six rounds closed: a caller that certifies a gate without an independent measurement — exit status (r1), the gate's own contract (r2), the gate's own SKIP token with no token-holding lane (r3), an explicit owner discarded (r3), the oracle's identity and the verification's outcome not on the receipt (r5–r6).

Ranked residuals

  1. P2 — unknown privacy is certified public (both critics): roadmap_check.sh's classifier treats every .private value other than the literal true as public, so a listing with .private missing/null yields repos=verified:13 with zero explicit false values; both callers accept it. Real GitHub responses always carry a boolean, so fixture-only today. → closed in round 7 (only explicit false counts; anything else is "unknown visibility", red).
  2. P3 — [99zb]'s identity check keys on the GNU banner, not BASH_VERSINFO (Fable): a genuine bash 3.2 with a non-GNU --version banner completes the audit and is failed "never named its interpreter" — a false RED, unreachable on any current lane. Fix shape: the gate prints oracle-major=N from BASH_VERSINFO[0] and the caller parses that.
  3. P3 — the [99zb] identity arm has no in-tree selftest (both; inside caveat 2): the only mechanical guard is Astra's reproducer under /tmp.
  4. P3 — under a public-only listing (github.token) a KNOWN_REPOS entry that flipped private is diagnosed "does not exist … not about the token" (both; inside caveat 1): still red, wrong reason; a listing with zero private rows is a public-only view and "absent" means absent-or-private.
  5. P3 — a self-echoing org listing forges repos=verified:13 (both; INSIDE the stated forged-receipt boundary): gutting the verifier is caught by the selftest pin; forging only the live path passes with zero listing calls.
  6. P3 — the daily workflow's "this lane exports GH_TOKEN" wording when both token variables are UNSET (both; caveat 4): correct failure, inaccurate wording.
  7. A user-owned fork running the daily audit goes RED by name (orgs/<user>/repos 404s → repos=skipped:org-listing-unavailable rejected by the live pin) — the safer direction; a behaviour change worth knowing.
  8. verified:N is not pinned to |KNOWN_REPOS| at the callers; a shrunken list is stricter, never a false green.
  9. README "~940K minimal binary" measures 951 KiB (inside the pinned ±10%; drift in progress).

Stated and pinned (do not re-file)

  • A gate that fabricates its own receipts is outside the caller's power (stated in [99zd], both gate headers, docs/CI.md).
  • The BUILTIN-FAMILIES class covers the seven-file doc set only; docs/TRACE.md and other executed-example docs are outside it.
  • Sanitizer shards hold no token by design (three redundant API walks per push).
  • DONE-cell equality is after whitespace/full-stop normalisation; lowercase repo names are red (typed case-sensitive KNOWN_REPOS).
  • The daily issue-triage.yml lanes (schedule, issues) are unobserved until the branch is on main.
Lingua principale
C
Stelle
3
Fork
7
Merge medio
3h 58m
PR unite (30g)
105

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 InauguralSystems/EigenScript

Tutte le issue di InauguralSystems/EigenScript

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.