cm_bot_v2

History

yiekheng 1c3d4ef893 fix(transfer): use dedicated /user/batch endpoint, alert+skip on fetch failure

Transfer bot was silently no-op'ing every Monday cycle since /user/
became paginated ({"rows": [...], "total": N}). The bot's silent
guard `len(items) if isinstance(items, list) else 0` collapsed every
contract mismatch and HTTP/JSON error into "0 items" with no signal.

- API: add /user/batch — bare-list, no pagination — for batch jobs.
  Keeps the paginated /user/ contract intact for the web UI.
- Bot: replace silent guard with raise_for_status + isinstance check.
  On any HTTP/JSON/contract failure, log + Telegram-alert + skip the
  cycle (next attempt in 10 min). Empty list still means "no work".
- Tests: 15 new tests pinning both sides of the contract, including a
  regression test that feeds the exact envelope shape that broke prod.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-04 08:31:08 +08:00

__init__.py

Refactor Docker layout for Gitea publishing

2025-10-19 22:22:55 +08:00

bot_cli.py

fix(hal): set_security_pin_api returns dict; cm_telegram now correct

2026-05-02 17:37:50 +08:00

cm_api.py

fix(transfer): use dedicated /user/batch endpoint, alert+skip on fetch failure

2026-05-04 08:31:08 +08:00

cm_bot_hal.py

fix(hal): set_security_pin_api returns dict; cm_telegram now correct