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

Synapse: increase presence ratelimit for tests #1394

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

anoadragon453
Copy link
Member

@anoadragon453 anoadragon453 commented Jan 24, 2025

This ratelimit is introduced in element-hq/synapse#18000 and causes some existing Sytests to fail for Synapse.

Increase the ratelimit in Sytest's Synapse config so tests pass again.


Note: I've re-pushed element-hq/synapse#18000 branch to https://github.com/element-hq/synapse/tree/set-presence-ratelimit so that the Sytest PR's CI will test that branch instead of develop.

This ratelimit is introduced in
element-hq/synapse#18000
and causes some existing Sytests to fail.

Increase the ratelimit in Sytest's Synapse config
so tests pass again.
Copy link
Contributor

@devonh devonh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shoud these be the same values as used for complement tests though?
ie. 9999 (element-hq/synapse@62b5e96)

@anoadragon453
Copy link
Member Author

Shoud these be the same values as used for complement tests though? ie. 9999 (element-hq/synapse@62b5e96)

Nah, 1000/second is more than enough for these tests (that typically only send <5 presence events). it may be nice to unify with Complement for consistency - but that should be a separate PR.

@anoadragon453 anoadragon453 merged commit 97f26d5 into develop Jan 24, 2025
7 checks passed
@anoadragon453 anoadragon453 deleted the set-presence-ratelimit branch January 24, 2025 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants