ENH: Review repeated warnings in out-of-core transfer loops
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
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- backend, performance
Línea de trabajo
Start by reviewing the source locations for the listed out-of-core transfer loops and identify which supported storage providers can emit repeated warnings. Reproduce representative cases, then compare runtime and diagnostic memory while checking that terminal errors and cancellation are preserved. The scope and warning-reporting policy are open decisions, so done requires an agreed policy and tests for the resulting behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Investigate how repeated storage warnings are retained by out-of-core transfer loops. This work is deferred from simplnx #1764 to a separate branch.
Source review found loops that merge warnings from each block or page. A storage provider that returns a warning for every transfer could make the retained warning list grow with the amount of work; repeated merging could also add time. No such repeated warnings from the normal HDF5 provider, resulting slowdown, or memory exhaustion has been observed in this investigation.
The agreed payload budget excludes Result, warning and error objects, and their message strings. This is therefore a possible diagnostic-memory and performance concern, not a demonstrated violation of that payload budget. Winding-transfer warnings have a separately approved limit on the current branch; that choice does not establish a policy for every other algorithm.
Examples identified during the review include normal and vertex-gather calculations, dihedral angle, smoothing, face orientation and misorientation, shared-feature-face metadata, centroids, triple-line extraction, and Avizo coordinate writing. This is not an exhaustive list. Determine which supported providers can produce repeated warnings and reproduce representative cases before selecting a warning-retention policy. Compare runtime and diagnostic memory, preserve terminal errors and cancellation, and test any proposed reporting behavior. The scope and reporting policy remain open decisions.
- 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