fix(mantis): wait for telegram desktop bootstrap · openclaw/openclaw@6da73ac
obviyus
·
2026-05-19
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -119,8 +119,10 @@ than Telegram-visible behavior`. Use this manifest shape and do not create
|
119 | 119 | `$OPENCLAW_TELEGRAM_USER_DRIVER_SCRIPT`, the workflow-provided `crabbox` |
120 | 120 | binary, and the workflow-provided local `ffmpeg`/`ffprobe`; do not generate, |
121 | 121 | install, or patch replacement proof tooling during the run. Use the same |
122 | | - proof idea for baseline and candidate. You may iterate and rerun if the |
123 | | - visual result is not convincing. |
| 122 | + proof idea for baseline and candidate. Let `start` return or fail on its |
| 123 | + own; do not kill it while Crabbox is still waiting for bootstrap. Use a long |
| 124 | + command timeout for `start`, `send`, `view`, and `finish`. You may iterate |
| 125 | + and rerun if the visual result is not convincing. |
124 | 126 | 7. Open Telegram Desktop directly to the newest relevant message with the |
125 | 127 | runner `view` command before finishing each recording. Keep the chat scrolled |
126 | 128 | to the bottom so new proof messages appear in-frame. |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -283,6 +283,10 @@ describe("Mantis Telegram Desktop proof workflow", () => {
|
283 | 283 | const prompt = readFileSync(PROMPT, "utf8"); |
284 | 284 | expect(prompt).toContain("$OPENCLAW_TELEGRAM_USER_PROOF_CMD"); |
285 | 285 | expect(prompt).toContain("do not run\n `pnpm qa:telegram-user:crabbox` directly"); |
| 286 | +expect(prompt).toContain("Let `start` return or fail on its\n own"); |
| 287 | +expect(prompt).toContain( |
| 288 | +"Use a long\n command timeout for `start`, `send`, `view`, and `finish`", |
| 289 | +); |
286 | 290 | }); |
287 | 291 | |
288 | 292 | it("runs the Mantis Codex agent in fast medium-effort mode", () => { |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
