-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Element (occasionally) repeatedly spams /sync
#25324
Comments
What is the response of the |
{"next_batch":"s306_5214_50_1_200_1_1_20_0_1","device_lists":{"changed":["@kirill:my.matrix.host"]},"device_one_time_keys_count":{"signed_curve25519":50},"org.matrix.msc2732.device_unused_fallback_key_types":["signed_curve25519"],"device_unused_fallback_key_types":["signed_curve25519"]} |
Not seeing any logs submitted from you Thanks for the /sync response though, looks like Synapse is sending an incremented next_batch so something is causing the sync to be retried and not persisted properly |
meh, maybe not matrix-org/synapse#15824. It's a bit hard to tell though: given the report there is no way to correlate request and response. If this happens again, please send debug logs from within Element. |
Steps to reproduce
Outcome
What did you expect?
To only request
/sync
upon whenWhat happened instead?
All these elements share the same
since
parameter.About 20,000 requests have been made in a matter of 30 seconds
I suspect this is an synapse issue, where long polling is incorrect.
Operating system
Arch Linux
Browser information
Chromium Version 112.0.5615.165
URL for webapp
localhost
Application version
Element version: 1.11.26 Olm version: 3.2.12
Homeserver
Synapse 1.82.0
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: