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

Equivalence harness gaps that block the L1->L4 ladder: abend injection, SEND/RECEIVE/RETURN/SYNCPOINT/DELAY faults, CEEDAYS, X6 WRITEQ

Abierto
  • ¿Algo no está bien?
#6,271 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
24/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
devtools, testing

Línea de trabajo

Read the equivalence harness and its fault/model assumptions, then inspect tests/equivalence/infeasible_outcomes.json and the #6072 programs cited for each gap. Start by choosing one checkbox-sized slice and tracing the relevant harness entry points and existing tests. Done means the harness records the fault or model, includes a test, and reports before/after coverage for the unblocked programs in the PR.

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

Descripción

claim:melek enhancement era:2 legacy-modernization priority: high scope:core testing

Why

The L1->L4 ladder (#6072) keeps ending at the same equivalence-harness limits rather than at missing scenarios: about 8 of the 33 ladder worker runs on 2026-10-22/23 stopped on one of the gaps below, and each run rediscovered it. Until the harness can inject or model these, the branches behind them can only be stated infeasible (when truly unreachable) or stay open.

Gaps (one checkbox = one slice; each cites the runs that hit it)

  • Abend injection: no way to make a called program / CICS command ABEND (incl. VSAM RLS abend) so HANDLE ABEND / abend paragraphs run (churn runs 6072-20261023T0128Z, 0354Z, 0448Z)
  • Failing SEND MAP / RECEIVE MAP / RETURN / SYNCPOINT: no RESP fault for these commands (0448Z)
  • DELAY fault (CBSA CRDTAGY1-5: the paragraphs behind a failed DELAY; 0128Z)
  • CEEDAYS model: CSUTLDPY date paragraphs in COACTUPC (90/95) need it (1553Z); stays within the CEEDAYS owner rulings (CRECUST stays refused)
  • Judging past an X6-refused WRITEQ (1701Z)
  • Paragraph-level infeasible outcomes in tests/equivalence/infeasible_outcomes.json (branch-level only today): CBPAUP0C 6000-EXIT was rediscovered in 5+ runs, CRDTAGY paragraphs stuck the same way (being added by the infeasible-outcomes tooling slice queued under #6072)

Acceptance

Each slice: the harness states the fault/model (oracle_assumptions entry where IBM documents the behaviour, refused by name where it does not), a test, and the #6072 programs it unblocks re-measured with before/after coverage in the PR body. Burned estates only; evidence levels, not "proven".

Part of #6072.

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

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.