AstrBot-Desktop/src-tauri
YokiiroBW 6060b968a7
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
feat(astrbot): record the message id value in the frame trace
The first capture answered the question the trace was built for and
eliminated it: all 77 plain frames of one reply carried a message_id, so
a reply splitting into two bubbles is not the event_id fallback in
F-34.

What remains depends on the value rather than its presence. If the id
changes partway through a reply then the client is correctly showing two
messages the server sent; if it stays the same then the split is ours,
in the historySessionId fallback that loads another session's history.
The id is an opaque row identifier, not content.

Also record the length of a string data payload. It separates "the
server streamed many small chunks" from "the server sent the reply in
one piece" without recording any text.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 01:54:17 +08:00
..
capabilities fix(tauri): grant the window controls the permissions they call 2026-07-27 01:19:42 +08:00
icons feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
src feat(astrbot): record the message id value in the frame trace 2026-07-27 01:54:17 +08:00
tests fix(tauri): grant the window controls the permissions they call 2026-07-27 01:19:42 +08:00
build.rs feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
Cargo.toml feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
tauri.conf.json fix(tauri): allow blob images in production csp 2026-07-26 22:28:35 +08:00