Five retention jobs have no attempt timeout

Abierto
#3,304 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
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend

Línea de trabajo

Start with the job registrations in src/FluentCMS.Core/DependencyInjection/FluentCmsServiceCollectionExtensions.cs:309 and :262-282, then read the retention loop in ActivityLog/ActivityRetentionJob.cs:53-70 and the related runner issues #3266, #3276, and #3285. Add a 10-minute attempt timeout for each of the five named jobs and check that timed-out work resumes on a later run without dead-lettering. Add a test that lists built-in jobs lacking timeouts.

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

Descripción

area:jobs type:bug

Problem

ActivityRetentionJob is registered without AttemptTimeout (src/FluentCMS.Core/DependencyInjection/FluentCmsServiceCollectionExtensions.cs:309), unlike JobRetentionJob and OutboxPruneJob, and the runner has no default. Its delete is batched and honours cancellation (ActivityLog/ActivityRetentionJob.cs:53-70) but the loop has no total bound. TrashPurgeJob, OidcPruneJob, UnverifiedMembersJob and IdempotencyRetentionJob are registered the same way (:262-282).

Proposal

Give the five jobs a 10-minute AttemptTimeout; each continues on its next run.

Done together with #3266, #3276 and #3285, which change the same runner and registrations.

Acceptance

  • Each retention job has an attempt timeout
  • A run stopped by the timeout leaves the remainder for the next run and is not dead-lettered
  • A test that lists registered built-in jobs without a timeout

Found in the code review of 17 Nov 2026.

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.