Skip to content
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

Messages are not sent but stay unsent in the chat without error #27005

Closed
kongo09 opened this issue Feb 13, 2024 · 9 comments
Closed

Messages are not sent but stay unsent in the chat without error #27005

kongo09 opened this issue Feb 13, 2024 · 9 comments
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@kongo09
Copy link

kongo09 commented Feb 13, 2024

Steps to reproduce

  1. Enter a room
  2. Try to send a message

Outcome

What did you expect?

Message is sent

What happened instead?

Message stays unsent, the read receipt bubble is an empty circle. No error message.

image

Operating system

Windows 11

Application version

Element version: 1.11.57 Crypto version: Olm 3.2.15

How did you install the app?

No response

Homeserver

element.io

Will you send logs?

Yes

@t3chguy
Copy link
Member

t3chguy commented Feb 13, 2024

What are the IDs of these events so the logs can be parsed?

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Feb 13, 2024
@kongo09
Copy link
Author

kongo09 commented Feb 13, 2024

room_id: !ZZVNrANIxNgftdLcEU:matrix.org

event_id:

  • $UT8A3ZrOChJILDAuTsGeSLbOMzDqYChWXByDsY_4HxY
  • $SngzwgNOul4DuqpbcR2nu8G-UQEQqWFLh3aOnXCgKBQ
  • $O97Z9v2HD6fyoMrdn5axCiUg5SQQAzEJeKIKDXDKNhA
  • $QcFurEZpMn_ZWMA9HD0pTYWyKaTSuL2ALx9uizw7xS8
  • $pyytdSIjQy8aFqtIrOXfImOFHP1ne5JsNhMbbuHCUsg

When I now send messages, they go through and appear above the stuck ones. There is no way to resend stuck ones.

@kongo09
Copy link
Author

kongo09 commented Feb 13, 2024

The recipient just tells me that he did indeed receive those five messages, was able to read and respond. I never got these responses, though.

@kongo09
Copy link
Author

kongo09 commented Feb 13, 2024

The same five messages seem to show as UTD of myself above in the timeline:

image

@t3chguy
Copy link
Member

t3chguy commented Feb 13, 2024

The messages being stuck at the bottom sounds like a server issue of missing remote echo, without remote echo the client has no way to know where the events fit in the order of the timeline as persisted as the server. Indeed in the logs for example UT8A3ZrOChJILDAuTsGeSLbOMzDqYChWXByDsY_4HxY I am not seeing a remote echo. Please open an issue with Synapse.

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2024
@kongo09
Copy link
Author

kongo09 commented Feb 13, 2024

How can it be a Synapse problem if it looks ok and normal on mobile?

@t3chguy
Copy link
Member

t3chguy commented Feb 13, 2024

Because the sync stream for all client's isn't the same, the transaction ID should only be sent back to the sender, and when Synapse is running in worker mode different sync workers can fall out of sync with each other causing some data to not be sent into certain streams. If you do a clear cache & reload it should fix the timeline for you in that room, the only way to debug it further would be to see the actual /sync responses but those aren't logged in the client.

@kongo09
Copy link
Author

kongo09 commented Feb 13, 2024

Understood. Is there any way to transfer the issue?

@t3chguy
Copy link
Member

t3chguy commented Feb 13, 2024

For someone with sufficient permissions in both repos, maybe (not me). But then that team will likely have insufficient information given their issue template will have been ignored

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants