Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Task marked completed despite input failures

未关闭
#7 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
56/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, python
领域
backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

bug
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
  1. Start a Recognize TaskProcessing job.
  2. Temporarily interrupt connectivity from recognize_backend to the Nextcloud instance.
  3. Let the backend attempt to process the task.
  4. 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
主要语言
Python
星标
3
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nextcloud/recognize_backend 的其他 Issue

查看 nextcloud/recognize_backend 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。