Michael Zhang 36bd3b60a3 fix: FETCHING lock not released after successful content sync ...

When fetch_articles_without_content() successfully fetches article content
via sync_article_content(), the article status stays at FETCHING(6)
permanently because the code only prints a success log but never resets
the status back to ACTIVE(1).

The fix: restore original status after successful content fetch, same as
the failure path already does.

Root cause: missing article.status = original_status_map.get(...) and
session.commit() in the success branch.

Impact: 88 articles stuck at status=6 on a deployed instance, invisible
to users despite having fully fetched content.

2026-05-10 03:12:12 +08:00

..

__init__.py

Fix

2025-11-24 21:25:32 +08:00

article.py

1.4.9-Fix

2026-03-31 14:17:04 +08:00

cascade_init_db.py

1.4.9-增加级联功能

2026-02-26 16:57:43 +08:00

cascade_init.py

1.4.9-增加级联功能

2026-02-26 16:57:43 +08:00

cascade_sync.py

1.4.9-Fix

2026-03-04 16:53:52 +08:00

cascade_task_dispatcher.py

1.4.9-Fix

2026-03-27 01:17:03 +08:00

failauth.py

1.4.8-修复过期消息二维码不显示

2025-12-25 17:23:13 +08:00

fetch_no_article.py

fix: FETCHING lock not released after successful content sync

2026-05-10 03:12:12 +08:00

mps.py

1.5.2-Fix

2026-04-20 20:58:05 +08:00

notice.py

feat: support bark for message tasks and system notices

2026-03-08 01:45:36 +08:00

taskmsg.py

Fix

2025-11-24 21:25:32 +08:00

webhook.py

1.4.9-Fix

2026-02-25 16:03:10 +08:00