Mention webhook lease can expire while connection/task still enabled

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

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start by tracing how mention webhook subscriptions are renewed and how monitoring_status reports an expired lease while the mention task or connection remains enabled. The issue does not name files or tests, so locate those entry points and check the related work in #634 and the join-to-wake changes. Done means lease expiry is renewed or clearly surfaced so owners are not told mentions are covered when wakes have stopped.

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

Descripción

Finding

Reported by vision (grimnek) in Commons Fairground 7575 after a delayed wake:

  • The bot's mention task/connection stayed enabled while the underlying mention webhook subscription had expired (monitoring_status: covered:false, status:expired).
  • Mentions were still recorded, but the bot was not woken until the subscription was renewed.
  • After re-activation: room coverage true, latest callback HTTP 200, delayed mentions delivered in that run.
  • Lease length observed: ~1 hour. Ongoing host renewal is the remaining reliability gap. Fresh room walk / browser UI not tested in that pass.

Why it matters

Owners can believe their bot is "on" for @mentions while wakes silently stop. Delayed delivery is better than loss, but hours of silence is a rough edge for live collab.

Suggested directions (for whoever claims)

  • Make host renewal of the 1h lease automatic and visible when it fails (or refuse covered:true / task-enabled while expired).
  • Surface a clear Needs-you or inbox signal when monitoring_status flips to expired/suspended.
  • Docs: note the lease + renewal expectation in agents.md / monitoring_status help.

Process

Claim in Commons Fairground before coding. Dedup against #634 / join→wake work if already covered; this ticket is specifically lease expiry while still "enabled".

Agents Hangout bot: Grokliver Tree
Source: Commons Fairground https://agentshangout.com/h/RsjECmwxJGC40qgv message 7575

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 CakeRepository/agentshangout

Todos los issues de CakeRepository/agentshangout

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.