Task marked completed despite input failures
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 56/100
Línea de trabajo
Start by tracing the TaskProcessing flow that downloads input files and marks a task complete; the issue does not name the relevant files or tests. Reproduce the failure by interrupting connectivity to Nextcloud and check whether failed inputs remain queued or are retried after connectivity returns. Done means a task with failed downloads is not reported as successfully completed and the inputs can be processed later.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
recognize_backend appears to mark TaskProcessing jobs as completed even when files could not be downloaded from the server.
So during a temporary network/firewall outage, the backend logged repeated download failures, but still reported the task as done.
Steps to reproduce
- Start a Recognize TaskProcessing job.
- Temporarily interrupt connectivity from recognize_backend to the Nextcloud instance.
- Let the backend attempt to process the task.
- Restore connectivity.
Expected behaviour
If one or more input files cannot be downloaded, the task should not be reported as successfully completed. Ideally, the task should fail/retry or the failed inputs should remain queued for later processing.
Actual behaviour
ERROR - Failed to download file 33942 for task 157: ... Connection refused
ERROR - Failed to download file 33943 for task 157: ... Connection refused
but then logs:
INFO - Task 157 done in 95.01s
The affected file IDs appear to be removed from the active processing flow and are not retried automatically. In my case, a manual occ recognize:recrawl was required to queue them again.
Server configuration
- Nextcloud 35.0.2
- Recognize Backend 1.0.6
- Recognize using TaskProcessing
- AppAPI/HaRP
- Backend running on a remote Docker host
- Lenguaje dominante
- Python
- Estrellas
- 3
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin 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 nextcloud/recognize_backend
-
bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
nextcloud/recognize_backend#6 · 2 comentarios · 2 reacciones ·
Todos los issues de nextcloud/recognize_backend
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
NousResearch/hermes-agent#147104 ·
Los mantenedores suelen responder en 1 día
-
[oblt-aw][autodoc] Document new required `shared-org-key` input for `obs-aw-dependency-review`Posiblemente ocupada @github-actions la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
bot-triaged module: inductor oncall: pt2 topic: fuzzer triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
getchaintips leaves out the active tip once a header is staged on it, where Core always lists itAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
btclib-org/btclib-node#2158 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
patrick-hudson/put.gd-desktop#979 · 1 comentario ·
Los mantenedores suelen responder en 1 día