Do we need references to pending records?

Abierto
  • ¿Algo no está bien?
#61 0 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
backend

Línea de trabajo

Start with the README’s “References” section, users.md, and the batch application design in issue #33; this issue does not name implementation files or tests. Decide whether pending-record references are needed for batches that submit chained reductions and then close their client. Done means the project has made that decision when the code is next touched or the batch application is designed.

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

Descripción

A request may reference an output of a record that is still pending, so a chain is submitted without waiting (README, "References"; stories S4 and C1):

centre = client.submit(BEAM_CENTRE, BeamCentreParams(...))     # pending
samples = client.submit([Request(IOFQ, IofQParams(centre=centre.ref('centre'), ...)) for ...])

The requirements know chaining (users.md: a beam centre feeds the sample reductions, and a person may chain by hand), but not chaining without waiting. A notebook can wait for the centre before it submits the samples. The backend pays for the pending case with dependents, waking, and the failure of a dependent when what it reads fails.

The case that may force it is batch reduction: a batch whose configuration chains reductions (users.md, "the result of one reduction sometimes feeds later ones") and whose client closes after submitting, as overnight batches do. Without pending references, such a batch needs a driver that stays alive to submit the later stages.

Decide when that code is next touched, or when the batch application is designed (#33). Moved from #28.

Lenguaje dominante
Python
Estrellas
0
Forks
1
Merge medio
9 h 23 min
PR fusionados (30 d)
65

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 scipp/essapps

Todos los issues de scipp/essapps

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.