- Ya
- 6 Agosti 2026, 22:13 UTC
- Mwandishi
- kamo
- Ahadi ya
- 09409fd
MediaService announced a new chat message twice — once when the row was saved, before any attachment existed, and once after the attachment rows committed. The bare announcement won the race, the client kept it and discarded the complete one behind it as a duplicate, so a just-sent image was missing from the message until the page was reloaded. Read off the CHAT_MESSAGES stream, the pair for one sent image is seq 1510 with "attachments": null and seq 1511 with the real list, 62ms apart. The server no longer announces a message it is still building (MediaService 90d46d2), and chat-core 0.1.2 treats a duplicate CREATE as new information rather than a repeat, so a client running against an instance that has not rolled over yet — or a mobile build on the same core — still shows the attachment.