Task marked completed despite input failures
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 56/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- Python
- Stelle
- 3
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nextcloud/recognize_backend
-
bug
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
nextcloud/recognize_backend#6 · 2 commenti · 2 reazioni ·
Tutte le issue di nextcloud/recognize_backend
Issue simili
-
[oblt-aw][autodoc] Document new required `shared-org-key` input for `obs-aw-dependency-review`Forse già presa @github-actions l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
getchaintips leaves out the active tip once a header is staged on it, where Core always lists itAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
btclib-org/btclib-node#2158 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
dbt-msft/dbt-sqlserver#897 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
Gathin23/cleanyourtv#2770 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Dao-AILab/flash-attention#3097 ·
I maintainer di solito rispondono entro 3 giorni