Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#290 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
4
Forks
0
Merge medio
1 d 8 h
PR fusionados (30 d)
36

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de drevendev/Scriptorium

Todos los issues de drevendev/Scriptorium

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.