Skip to content

fix: isolate per-rule errors in scheduled automation scan - #911

Open
AlexCXC wants to merge 1 commit into
masterfrom
fix-isolate-scheduled-rule-errors
Open

AlexCXC wants to merge 1 commit into
masterfrom
fix-isolate-scheduled-rule-errors

Conversation

@AlexCXC

@AlexCXC AlexCXC commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Run each scheduled automation rule inside its own try/except so that db/redis connection failures for one rule do not abort the whole scan. Materialize the rule query with fetchall() and close the query session before processing, and recreate the per-rule session on failure.

Run each scheduled automation rule inside its own try/except so that
db/redis connection failures for one rule do not abort the whole scan.
Materialize the rule query with fetchall() and close the query session
before processing, and recreate the per-rule session on failure.

@seafile-dev seafile-dev left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: Comment

Warnings:

  • 缺少覆盖 Redis/数据库异常隔离行为的回归测试;已在行内说明。
    Suggested fix: 为 scan_rules 注入可控的规则列表与依赖,模拟某条规则的配额查询抛出 ConnectionError,断言后续规则仍会入队,并覆盖下一条规则使用新 session 的场景。

try:
for rule in rules:
db_session = None
for rule in rules:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Warning] 缺少故障隔离回归测试

Why this matters:
本次修改修复的是 Redis/数据库读取异常导致后续定时规则整体不执行的生产故障,但 PR 未新增覆盖该异常路径的测试。后续调整 session 生命周期或异常处理时,循环隔离与失败后重建 session 的关键行为可能再次退化而不被 CI 发现。

Suggested fix: 为 scan_rules 添加测试,模拟某条规则的 is_exceed 抛出连接异常,断言后续规则仍入队;同时验证下一次查询会使用新建的 session。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants