Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Rename test case method to `add_hashes_and_signatures_from_other_server` ↵ | David Robertson | 2022-07-12 | 1 | -3/+3 |
| | | | | (#13255) | ||||
* | Fix inconsistencies in event validation (#13088) | Richard van der Hoff | 2022-06-17 | 1 | -1/+0 |
| | |||||
* | Wait for lazy join to complete when getting current state (#12872) | Erik Johnston | 2022-06-01 | 1 | -1/+3 |
| | |||||
* | Rename storage classes (#12913) | Erik Johnston | 2022-05-31 | 1 | -4/+5 |
| | |||||
* | Refactor `EventContext` (#12689) | Erik Johnston | 2022-05-10 | 1 | -1/+3 |
| | | | | | | | | | | Refactor how the `EventContext` class works, with the intention of reducing the amount of state we fetch from the DB during event processing. The idea here is to get rid of the cached `current_state_ids` and `prev_state_ids` that live in the `EventContext`, and instead defer straight to the database (and its caching). One change that may have a noticeable effect is that we now no longer prefill the `get_current_state_ids` cache on a state change. However, that query is relatively light, since its just a case of reading a table from the DB (unlike fetching state at an event which is more heavyweight). For deployments with workers this cache isn't even used. Part of #12684 | ||||
* | Optimise `_get_state_after_missing_prev_event`: use `/state` (#12040) | Richard van der Hoff | 2022-04-01 | 1 | -0/+225 |
If we're missing most of the events in the room state, then we may as well call the /state endpoint, instead of individually requesting each and every event. |