Fix Telegram rich progress detail updates#93698
Merged
Merged
Conversation
openclaw-barnacle
Bot
added
channel: telegram
obviyus
force-pushed
the
codex/fix-telegram-rich-progress-details
branch
from
June 16, 2026 16:26
78a2715 to
a0629c2
Compare
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: Fix Telegram rich progress detail updates This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
obviyus
force-pushed
the
codex/fix-telegram-rich-progress-details
branch
3 times, most recently
from
June 16, 2026 17:15
f1b8168 to
cff6b27
Compare
obviyus
force-pushed
the
codex/fix-telegram-rich-progress-details
branch
from
June 16, 2026 17:17
cff6b27 to
77da499
Compare
Contributor
Author
|
Merged via squash.
Thanks @obviyus! |
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jun 17, 2026
Merged via squash. Prepared head SHA: 77da499 Co-authored-by: obviyus <[email protected]> Co-authored-by: obviyus <[email protected]> Reviewed-by: @obviyus
crh-code
pushed a commit
to crh-code/openclaw
that referenced
this pull request
Jun 18, 2026
Merged via squash. Prepared head SHA: 77da499 Co-authored-by: obviyus <[email protected]> Co-authored-by: obviyus <[email protected]> Reviewed-by: @obviyus
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bash completed.parse_mode: HTMLtext.Verification
node scripts/run-vitest.mjs src/plugin-sdk/channel-streaming.test.ts src/channels/streaming.test.ts extensions/telegram/src/draft-stream.test.tsnode scripts/run-tsgo.mjs -p test/tsconfig/tsconfig.extensions.test.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/extensions-test.tsbuildinfopnpm exec oxfmt --check --threads=1 src/channels/streaming.ts src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/draft-stream.ts extensions/telegram/src/draft-stream.test.ts extensions/telegram/src/bot-message-dispatch.test.tsgit diff --check.agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main-> clean, no accepted/actionable findings34408, SUT reply34409,OPENCLAW_E2E_OKrichMessages: trueand rich progress config: driver message34413, SUT reply34414,OPENCLAW_E2E_OKKnown unrelated main drift:
node scripts/run-vitest.mjs extensions/telegram/src/bot-message-dispatch.test.tscurrently fails onorigin/mainwith the same two existing assertions (keeps same-message block chunks...,suppresses non-terminal final error warnings...).