179a59bf16
The 9P client splits writes larger than msize into multiple Twrite messages with increasing offsets. The server was dispatching each Twrite immediately, so only the first chunk was ever processed — causing JSON parse failures for payloads exceeding msize. Fix: accumulate all Twrite data into a per-fid writeBuf, then dispatch the fully-assembled payload in Tclunk. Tclunk can return Rerror if dispatch fails, preserving error reporting to the caller. This unblocks large bead descriptions/comments and message bodies without any msize negotiation changes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| backend | ||
| backends | ||
| debug | ||
| eventbus | ||
| logging | ||
| mailbox | ||
| maildir | ||
| p9 | ||
| sandbox | ||
| session | ||
| supervisor | ||