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> |
||
|---|---|---|
| .. | ||
| capabilities | ||
| icons | ||
| src | ||
| tests | ||
| build.rs | ||
| Cargo.toml | ||
| tauri.conf.json | ||