惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

P
Proofpoint News Feed
云风的 BLOG
云风的 BLOG
Apple Machine Learning Research
Apple Machine Learning Research
Hugging Face - Blog
Hugging Face - Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Google DeepMind News
Google DeepMind News
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
雷峰网
雷峰网
B
Blog
月光博客
月光博客
博客园 - 【当耐特】
WordPress大学
WordPress大学
Microsoft Azure Blog
Microsoft Azure Blog
I
InfoQ
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
Jina AI
Jina AI
博客园 - Franky
MyScale Blog
MyScale Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Last Week in AI
Last Week in AI
B
Blog RSS Feed
H
Help Net Security

Recent Commits to openclaw:main

test: merge chat side-result checks · openclaw/openclaw@ddd2c2a test: merge cron history checks · openclaw/openclaw@f7eb746 test: merge responsive navigation shell checks · openclaw/openclaw@c2e4b47 docs(changelog): add codex oauth fixes · openclaw/openclaw@628e6cd test: merge navigation routing cases · openclaw/openclaw@5d8cecb Tests: mock channel registry bundled fallback · openclaw/openclaw@2b08233 Secrets: avoid broad web search discovery for single plugin config · openclaw/openclaw@a464f59 test: merge config view browser checks · openclaw/openclaw@20cf511 fix(status): align oauth health with runtime · openclaw/openclaw@eed7116 feat: add macOS screen snapshots for monitor preview (#67954) thanks … · openclaw/openclaw@f377db1 fix: report shared auth scopes in hello-ok (#67810) thanks @BunsDev · openclaw/openclaw@0b6c39b Auto-reply: avoid eager bundled route fallback · openclaw/openclaw@3ea1bf4 Tests: narrow session binding contract setup · openclaw/openclaw@54e4e16 fix(macOS): enable undo/redo in webchat composer text input (#34962) · openclaw/openclaw@00951dc Tests: speed up channel setup promotion · openclaw/openclaw@82b529a Docs: refresh agent instructions · openclaw/openclaw@5775fe2 fix(auth): serialize OAuth refresh across agents to fix #26322 (#67876) · openclaw/openclaw@8e79080 test: allow ollama public surface boundary test · openclaw/openclaw@7d4f1a6 Docs: add test performance guardrails · openclaw/openclaw@89706d3 Tests: restore context-engine usage proof · openclaw/openclaw@e4c4f95 Tests: slim context engine runtime coverage · openclaw/openclaw@74c198f ci: retry failed custom checkouts · openclaw/openclaw@0ee5baf test: trim duplicate provider auth onboarding cases · openclaw/openclaw@1ffc02e matrix: fix sessions_spawn --thread subagent session spawning (#67643) · openclaw/openclaw@1ce2596 test: reduce auth choice fixture churn · openclaw/openclaw@857b9cd test: mock health status config boundaries · openclaw/openclaw@9d5ab4a test: mock onboard config io boundary · openclaw/openclaw@299694d test: mock legacy state plugin boundaries · openclaw/openclaw@2713089 test: mock channel install boundaries · openclaw/openclaw@b945248 test: mock doctor preview channel boundaries · openclaw/openclaw@b1a3ad4
fix(telegram): classify sendChatAction 401 by structured ...
ZOOWH · 2026-06-19 · via Recent Commits to openclaw:main

@@ -301,4 +301,94 @@ describe("createTelegramSendChatActionHandler", () => {

301301

await handler.sendChatAction(444, "typing");

302302

expect(fn).toHaveBeenCalledTimes(3);

303303

});

304+305+

it("treats a structured 429 with retry_after=401 as transient, not as a 401 suspension", async () => {

306+

// grammY renders this as: "Call to 'sendChatAction' failed! (429: Too Many Requests: retry after 401)"

307+

// The substring "401" in the message must NOT trigger the 401 suspension path.

308+

const make429WithRetryAfter401 = () =>

309+

Object.assign(

310+

new Error("Call to 'sendChatAction' failed! (429: Too Many Requests: retry after 401)"),

311+

{ error_code: 429, parameters: { retry_after: 401 } },

312+

);

313+314+

let now = 0;

315+

const fn = vi.fn().mockRejectedValue(make429WithRetryAfter401());

316+

const logger = vi.fn();

317+

const handler = createTelegramSendChatActionHandler({

318+

sendChatActionFn: fn,

319+

logger,

320+

maxConsecutive401: 3,

321+

now: () => now,

322+

});

323+324+

// All calls should fail but as transient errors, NOT 401 errors

325+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("429");

326+

// Advance past the transient cooldown (retry_after=401 → 401000ms)

327+

now += 402_000;

328+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("429");

329+

now += 402_000;

330+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("429");

331+332+

// Handler must NOT be suspended — this is a transient 429, not a 401

333+

expect(handler.isSuspended()).toBe(false);

334+335+

// Must NOT have logged the CRITICAL token-deletion alarm

336+

const criticalLogs = logger.mock.calls.filter(([msg]) => String(msg).includes("CRITICAL"));

337+

expect(criticalLogs).toEqual([]);

338+

});

339+340+

it("detects a structured Telegram 401 error by error_code, not by message substring", async () => {

341+

const makeStructured401 = () => Object.assign(new Error("Unauthorized"), { error_code: 401 });

342+343+

const fn = vi.fn().mockRejectedValue(makeStructured401());

344+

const logger = vi.fn();

345+

const handler = createTelegramSendChatActionHandler({

346+

sendChatActionFn: fn,

347+

logger,

348+

maxConsecutive401: 2,

349+

});

350+351+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("Unauthorized");

352+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("Unauthorized");

353+354+

expect(handler.isSuspended()).toBe(true);

355+

expect(logger.mock.calls.at(-1)).toEqual([

356+

"CRITICAL: sendChatAction suspended after 2 consecutive 401 errors. Bot token is likely invalid. Telegram may DELETE the bot if requests continue. Replace the token and restart: openclaw channels restart telegram",

357+

]);

358+

});

359+360+

it("does not misclassify a plain error whose message contains '401' as a 401 error", async () => {

361+

// A plain Error (no error_code) with "401" in its message should NOT

362+

// trigger the 401 path, since bare substring matching was the root cause

363+

// of #94787. Only "unauthorized" is the fallback for non-Telegram errors.

364+

const fn = vi.fn().mockRejectedValue(new Error("401 Too Many Requests: retry after"));

365+

const logger = vi.fn();

366+

const handler = createTelegramSendChatActionHandler({

367+

sendChatActionFn: fn,

368+

logger,

369+

maxConsecutive401: 3,

370+

});

371+372+

// This is neither a recognized 401 nor a recognized transient → falls to

373+

// the "else" branch (clears transient cooldown, re-throws).

374+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("401");

375+

expect(handler.isSuspended()).toBe(false);

376+

});

377+378+

it("recognizes non-Telegram 401 via 'unauthorized' in message as a 401", async () => {

379+

// A plain Error without error_code but with "unauthorized" should still

380+

// be classified as 401 (this is the intentional fallback path).

381+

const fn = vi.fn().mockRejectedValue(new Error("Unauthorized access"));

382+

const logger = vi.fn();

383+

const handler = createTelegramSendChatActionHandler({

384+

sendChatActionFn: fn,

385+

logger,

386+

maxConsecutive401: 2,

387+

});

388+389+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("Unauthorized");

390+

await expect(handler.sendChatAction(123, "typing")).rejects.toThrow("Unauthorized");

391+392+

expect(handler.isSuspended()).toBe(true);

393+

});

304394

});