$ the-wire · showcase
Fixes for stale DashScope downloads and Telegram forward origins
By RepoJournal · Filed · About OpenClaw
Two OpenClaw fixes landed today: DashScope video downloads no longer hang on stalled CDN bodies, and Telegram debounce batches preserve per-message forward origins.
OpenClaw fixed two download pathologies in DashScope-compatible video generation [1]. A stalled CDN body after headers returned now fails on a chunk-idle timeout instead of waiting the full request budget, and an exhausted deadline can no longer initiate network I/O because the remaining-deadline check moved before the guarded fetch. Operators running DashScope video generation should upgrade to get bounded downloads and fail-closed behavior on deadline exhaustion.
Telegram message forwarding now keeps per-message source attribution across the inbound debounce window [2]. Previously, mixed and multi-origin batches could be presented as the forwarding user's text or attributed entirely to the first source; the debounce path now carries original messages into the Telegram context owner for correct formatting. [2]
Provider catalogs for zai, kimi, moonshot, and xai were refreshed against July 2026 vendor docs [3]. Z.AI GLM-5.x pricing is corrected and Kimi/Moonshot setup hints no longer reference retired K2.6 wording or embedded volatile prices. xAI guidance now includes Grok Build CLI and the long-context pricing caveat. [3]
Action items
- → Upgrade OpenClaw to include the DashScope download timeout and deadline check fix before your next video-generation workload openclaw/openclaw [plan]
- → Review Telegram debounce handling for forward-origin attribution and carry the fix forward in your deployment openclaw/openclaw [plan]
- → Refresh any pinned vendor model catalogs or setup hints for zai, kimi, moonshot, and xai openclaw/openclaw [monitor]
References
- [1] fix(video-generation): DashScope downloads hang when CDN body stalls after headers ↗ openclaw/openclaw
- [2] fix(telegram): preserve forward origins in debounce batches ↗ openclaw/openclaw
- [3] fix(providers): refresh zai/kimi/moonshot/xai catalogs against July 2026 vendor docs ↗ openclaw/openclaw