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

Context Agent can stop claiming tasks while /trigger still returns 200

Abierto
  • ¿Algo no está bien?
#266 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@dberardo-com ya está trabajando en esto.

Desde el 13/10/2026.

  • #267 de @dberardo-com — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
kubernetes, python
Área
backend

Línea de trabajo

Start by reading background_thread_task() and next_task(), the polling entry points named in the issue. Check how the background poller is started and what happens when task acquisition stalls or exits; the report does not identify a test file. Done means the poller is supervised, task acquisition is bounded, and unexpected stops are logged, with processing able to continue after a transient backend failure.

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

Descripción

bug

I'm running Context Agent 2.9.1 with Nextcloud 35 on Kubernetes.

I ran into a situation where new tasks stayed SCHEDULED for over 10 minutes, even though /trigger returned HTTP 200 and the ExApp pod remained healthy. The agent wasn't logging any new task pickups or obvious polling errors.

Looking at background_thread_task(), the poller is started without supervision and next_task() has no explicit timeout. If that coroutine exits or gets stuck, the HTTP server can apparently remain healthy.

I tried a local patch with a supervised polling loop, a timeout around next_task(), and some basic lifecycle logging. I also tested temporarily disconnecting my LocalAI backend: the model request failed as expected, but the agent continued processing new requests after connectivity was restored, without restarting the pod.

I can't confirm that a LocalAI failure caused the original stuck poller, but the current polling implementation seems worth hardening.

Would it make sense to add supervision, bounded task acquisition, and better logging when the background poller unexpectedly stops?

Lenguaje dominante
Python
Estrellas
26
Forks
20
Merge medio
2 d 9 h
PR fusionados (30 d)
4

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 nextcloud/context_agent

Todos los issues de nextcloud/context_agent

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.