Five retention jobs have no attempt timeout

未关闭
#3,304 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

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.

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

描述

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.

主要语言
C#
星标
569
派生
107
平均合并
2 小时 49 分钟
30 天内合并 PR
397

环境准备

从这里开始

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

fluentcms/FluentCMS 的其他 Issue

查看 fluentcms/FluentCMS 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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