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

keep source file and reader provenance on image specs

Abierto
  • ¿Algo no está bien?
#5,510 1 comentario 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
computer-graphics

Línea de trabajo

Start by tracing the higher-level ImageBuf and ImageCache read paths, including how cached subimages and native specs are produced, then inspect ImageOutput::check_open() and the ImageInput boundary. Verify that source path and reader format reach the specified specs and ImageBufAlgo results, while raw ImageInput specs remain unchanged. Done means both attributes are removed before in-tree writer headers are constructed.

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

Descripción

ImageBuf::name() and ImageBuf::file_format_name() identify the source file
and reader, but that information does not travel with a copied spec, an
ImageCache result, or an ImageBufAlgo result. Applications must track it out
of band.

Proposal

  1. Add oiio:SourcePath and oiio:SourceFileFormat to specs from higher-level file
    reads. A direct ImageBuf read records the supplied name. ImageCache
    records the search-path-resolved name. The format comes from the reader's
    format_name().
  2. Add them to every cached subimage and the native spec. Because they are spec
    attributes, ordinary spec copies and ImageBufAlgo results retain them. Raw
    ImageInput specs remain unchanged.
  3. As oiio: attributes they are hints, which writers already don't store in
    files (the FITS writer is fixed to follow that convention too).
  4. Do not use provenance to drive behavior yet. Applying FileRules to
    oiio:SourcePath, especially after combining several inputs, needs separate
    policy review.

Behavior this changes

Specs returned through ImageBuf and ImageCache expose their source path and
reader format. The values survive normal spec-carrying operations, but neither
attribute is serialized to output files.

Are these the right names and higher-level-read boundary?

Assisted-by: OpenAI Codex (GPT-5.6 Sol)

Lenguaje dominante
C++
Estrellas
2.4k
Forks
716
Merge medio
2 d 9 h
PR fusionados (30 d)
91

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 AcademySoftwareFoundation/OpenImageIO

Todos los issues de AcademySoftwareFoundation/OpenImageIO

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.