-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yesterday is after today #27003
Comments
Events in Matrix are eventually consistent, this is normal and can happen if your server or the originating server is having federation issues causing the events to be delivered late. |
It is only the main matrix server which i use, no federation or logins on other servers. |
There is no "main" server, if you mean matrix.org then I suggest [email protected] |
How many hours is the expected time for the "eventually consistent" to show things in the right order? Is a day too little? |
The eventual consistency happens on the server, not the client. The client is fed with a linearised stream of events, abstracting the complexity, though sometimes ends up receiving out-of-order events from the server. |
This client is on 24/7 and i wrote that message that is in the wrong place yesterday ca 20 hours ago on the very same client that is showing it out of order. My other android client is showing it correctly. |
Restarted client and it now shows the stuck message as a not sent edit with a warning icon. |
I suggest Settings > Help & About > Clear cache and reload Different clients might see different things as matrix.org has many workers and your clients may be being served by different such workers causing a mismatch. |
Steps to reproduce
Outcome
What did you expect?
For yesterday to be before today
What happened instead?
Yesterday is after today (monday)
Operating system
Arch linux
Application version
Element desktop 1.11.54
How did you install the app?
distro package manager
Homeserver
matrix.org
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: