J'ai des problèmes pour envoyer des messages directs ou des messages de canal en succession rapide

j.jaffeux · Août 27, 2025, 11:26

J’expérimenterai ceci demain :

github.com/discourse/discourse

FIX: client based chat message timestamp

main ← frontend-timestamp

opened 11:25PM - 27 Aug 25 UTC

jjaffeux

+170 -2

Uses the timestamp at the moment where the user hits send for the created_at val…ue of the chat message. This should ensure very consistent ordering. The implementation is simple: - collects the timestamp and send it in the request (client_created_at) - if client_created_at is present and valid, set it as created_at when creating the message I suspect that we could end up in a situation where a message is routed to a slower worker and even if sent before an other message could end up being persisted later which would cause ordering issues.

Et si cela se passe bien, je le fusionnerai plus tard dans la semaine.

Sujet		Réponses	Vues
Chat messages appearing in wrong order Bug chat	16	336	Janvier 26, 2025
Moving chat messages to a new channel jumbled them all up Bug chat	15	939	Juin 12, 2022
Chat: inconsistent time format for consecutive messages from the same user UX chat	2	51	Juin 12, 2025
Replies on channel dropping to top Support chat	4	225	Mai 28, 2024
Chat messages not showing up unless I refresh or switch channels Bug chat	9	1529	Juillet 21, 2024

J'ai des problèmes pour envoyer des messages directs ou des messages de canal en succession rapide

Sujets connexes