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

Crucible Path Independence: run the two parent-path scans concurrently (6.4 min serial step)

Cerrado
  • ¿Algo no está bien?
#5,500 4 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
performance, testing

Línea de trabajo

Start with tests/tools/crucible_path_check.py, especially main() and scan(), and inspect crucible-path-independence.yml to understand the timed step. First measure whether one galaxyscope scan saturates the 4-vCPU runner, then assess the independent scans and required error handling. Done means the full comparison and failure cases still work, with before and after step timings recorded in the PR body.

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

Descripción

ci-cd github-actions performance scope:infra

Measured (2026-10-16 to 2026-10-18, last 8 successful PR runs): crucible-path-independence.yml takes 7.1 min median, 7.5 max. Of that, 6.4 min is the step "Scan the corpus from two parent paths" (tests/tools/crucible_path_check.py --corpus ../language-crucible/data).

Where the time goes: in main(), scan(neutral_dir, ...) and then scan(special_dir, ...) run one after the other. Each is a full python -m gitgalaxy.galaxyscope subprocess over the staged language-crucible copy. The two scans are independent: different staged directories and different output dirs.

Proposed
  • Run the two scan() calls at the same time, for example with two subprocess.Popens or a 2-worker ThreadPoolExecutor around scan. Keep the error handling: an unreadable output is still a finding, and neutral_error != special_error still counts as a diff.
  • First measure how many cores one galaxyscope scan already uses on the 4-vCPU runner. If it already saturates them, parallel scans gain little. In that case, look at whether the scan can drop work that never depends on the parent path (e.g. snapshot outputs not compared), and record the finding here.
  • Unit test: the check still reports a diff when one side differs, and still fails when one side's output can't be read (fake scan).

Rule: the same corpus is scanned from both parent paths, and the full comparison runs.

Acceptance: the step's time before and after, in the PR body (target ~3.5–4 min).

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 5 min
PR fusionados (30 d)
976

Preparar el entorno

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 squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.