-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Creating a handful (~3) of rooms, for example to populate a new Space in Element Web, leads to running into rate limits #14312
Comments
Is #14307 attempting to fix this? |
I don't know, but it doesn't pass |
These places contribute to the rate limiting in the above test:
One might argue that we shouldn't ratelimit the creation of events whilst creating a room at all, because then you easily end up with a partially-created room which is very janky. I'd be tempted to rate limit the room's creation but not the events that go inside (?) |
This is where the rate limits used to happen in v1.68.0:
It appears that there was 1 event per room being rate limited, plus the room creation itself (?) |
I think this likely makes sense. |
Fixed by #14314. |
With default rate limiting values, we used to be able to create at least 3 rooms in one go. The new Space screen in Element Web depends on this (element-hq/element-web#23620) and breaks if any of those room creations are rate limited, as they are now (v1.70.0).
The following test case demonstrates this:
Bisecting, the following commit is what made the above fail because of the rate limit: 8ab16a9 'Persist CreateRoom events to DB in a batch (#13800)' in v1.69.0.
We should try to revert rate limiting to behave the same as before or closely enough that this basic use case is not broken.
The text was updated successfully, but these errors were encountered: