ENH: Retire unchecked paths in shared image engines
Los mantenedores suelen responder en 6 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by reviewing the finite-difference and recursive Gaussian image engines, the checked paths for Curvature Flow and Smoothing Recursive Gaussian, and PR #1888's review discussion; the issue does not name file paths or tests. Trace how successful transfer warnings and later failures are handled, then compare affected filter results in in-core and out-of-core modes, including outputs, precision, cancellation, and diagnostics. Done means warnings are retained in order, the original failure is preserved, and the legacy unchecked modes are retired only after the numerical contracts are verified.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Retire the unchecked paths in the finite-difference and recursive Gaussian image engines. Successful read or write operations can return warnings. Some default engine paths discard those warnings when they check only for errors. The checked paths added for Curvature Flow and Smoothing Recursive Gaussian retain diagnostics.
Start with warning propagation. Then confirm the numerical contracts for the sibling filters before removing the legacy conversion paths. The mode switches also affect numeric narrowing, so review this migration against existing filter results.
Acceptance criteria
- Keep each successful transfer warning once, including when a later transfer fails. Preserve the original failure and verify the diagnostic order with a test store that emits distinct warnings.
- Verify the affected filters in both in-core and out-of-core configurations. Check outputs, precision, cancellation, and diagnostics before retiring the unchecked modes.
- Keep filter-specific diagnostics at their callers and apply the coding knowledge base rule on Result handling.
Related work
PR #1888 review identified these engine paths. #1868 inventories other dropped results. #1929 evaluates the cost of retaining repeated transfer warnings.
- Lenguaje dominante
- C++
- Estrellas
- 18
- Forks
- 15
- Merge medio
- 4 d 23 h
- PR fusionados (30 d)
- 42
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de BlueQuartzSoftware/simplnx
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
BlueQuartzSoftware/simplnx#1987 ·
Los mantenedores suelen responder en 6 días
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
BlueQuartzSoftware/simplnx#1980 ·
Los mantenedores suelen responder en 6 días
-
Testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
BlueQuartzSoftware/simplnx#1979 ·
Los mantenedores suelen responder en 6 días
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
BlueQuartzSoftware/simplnx#1978 ·
Los mantenedores suelen responder en 6 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
BlueQuartzSoftware/simplnx#1945 ·
Los mantenedores suelen responder en 6 días
Todos los issues de BlueQuartzSoftware/simplnx
Issues similares
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
26.04 bug dark-mode Easy Hack impress symptom: visual
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
CollaboraOnline/online#16421 · 1 comentario ·
-
area/cs bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
ydb-platform/ydb#59881 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
documentation enhancement lua server
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100