A burst of deliveries to one webhook drains at about one per timeout

Abierto
#3,268 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Read src/plugins/FluentCMS.Plugins.Webhooks/WebhookDeliveryJob.cs:142-151 and WebhookQueueTests.TwoDeliveriesToOneWebhookNeverRunAtOnce first. Trace how a completed delivery schedules the next waiting attempt and how attempts are ordered by event time. Done means bursts reach a fast receiver at roughly its response time per event, in event order, without waiting jobs rerunning while another attempt is in flight.

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

Descripción

performance plugin type:bug

Problem

While a webhook has an attempt in flight, WebhookDeliveryJob (src/plugins/FluentCMS.Plugins.Webhooks/WebhookDeliveryJob.cs:142-151) reschedules every other attempt for it to busy.CreatedAt + Timeout plus jitter, the worst-case end of the send. WebhookQueueTests.TwoDeliveriesToOneWebhookNeverRunAtOnce asserts that wait. 1,000 events to a receiver that answers in 200 ms take hours; each round re-runs every waiting job (O(N²)) on the webhooks queue all sites share; jitter reorders events of one entry.

Proposal

Let a finished attempt wake the oldest waiting one (or keep a per-webhook FIFO drained by one job), order attempts by event time, and back off from now rather than from the worst case if polling stays.

Acceptance

  • N events to a fast receiver are delivered in about N times its response time, in event order
  • Waiting attempts do not re-run while one is in flight

Found in the code review of 17 Nov 2026 (P1).

Lenguaje dominante
C#
Estrellas
569
Forks
107
Merge medio
2 h 49 min
PR fusionados (30 d)
397

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 fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.