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

Adopt private batch analysis with deterministic manifests and failure-safe reports

Chiusa
  • Qualcosa non va?
#290 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
cli

Direzione di ricerca

Start by inspecting and deduplicating any surviving batch Workbench prototype material against the current code, then trace the existing build_local_analysis() contract. Define the bounded manifest, output and failure behavior, and verify the installed-wheel end-to-end cases listed in Acceptance, including every generated report and index link. Done means deterministic, retryable batch reports and a source-free index with the documented privacy limits; keep the work in the existing project queue.

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

Descrizione

Deferred Workbench debt

The canonical README and historical #274 record identify batch Workbench prototypes as unpublished. The accepted #273/#276 path processes one UTF-8 manuscript, and #279/#288 compares two existing reports; neither is a batch runner. Open/closed issue searches found no dedicated batch-delivery issue. Original prototype bytes were not recovered here, so previous local success claims require revalidation.

User outcome

Analyze an explicitly selected set of local manuscripts through the existing canonical Reader and inspect one deterministic, source-free index of reports and failures. No implicit directory crawling, manuscript upload or public corpus enrollment.

Acceptance

  • Reuse build_local_analysis() and its versioned metric/source/dictionary contract; no shadow analyzer or second long-lived control plane.
  • Accept an explicit bounded manifest or file list. UTF-8 first; EPUB may follow #289 and must not block the independent batch slice.
  • Bounded total input and file count; regular-file/symlink protections; deterministic ordering and collision-resistant report identities. Never follow links or traverse unspecified trees.
  • Preserve existing destinations. Invalid input must not destroy another valid report or the previous complete index. Specify exit codes and partial-failure semantics; interrupted runs are safely retryable without duplicate outputs.
  • Index/export contains declared source hashes, statuses and relative output routes, not manuscript text or undisclosed private absolute paths. Unknown and failed items never acquire zero metrics or PASS.
  • Actual installed-wheel end-to-end tests for two distinct texts, duplicate input, conflicting names, malformed/special/oversized input, existing output and interrupted/repeated runs. Check every generated report/index link.
  • Document CLI usage, privacy, storage and reprensentativeness limitations; do not publish the registry, activate Pages or claim corpus/parity completion. M2 remains 0/5.

First inspect/deduplicate surviving prototype material against current code. Keep priority in the existing project queue; this issue is a retained future product scope, not an authorization to fork another worker.

Lingua principale
Python
Stelle
4
Fork
0
Merge medio
1g 8h
PR unite (30g)
36

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 drevendev/Scriptorium

Tutte le issue di drevendev/Scriptorium

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.