- Jun 17, 2022
-
-
David Robertson authored
-
Shay authored
Update opentracing docs to reference the configuration manual rather than the configuation file. (#13076)
-
Richard van der Hoff authored
-
Richard van der Hoff authored
* Extend the auth rule checks for `m.room.create` events ... and move them up to the top of the function. Since the no auth_events are allowed for m.room.create events, we may as well get the m.room.create event checks out of the way first. * Add a test for create events with prev_events
-
Patrick Cloke authored
-
reivilibre authored
* Fix type error introduced accidentally by #13045 * Newsfile Signed-off-by:
Olivier Wilkinson (reivilibre) <oliverw@matrix.org>
-
Richard van der Hoff authored
-
Quentin Gliech authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Quentin Gliech authored
Signed-off-by:
Quentin Gliech <quenting@element.io>
-
Sean Quah authored
When we fail to persist a federation event, we kick off a task to remove its push actions in the background, using the current logging context. Since we don't `await` that task, we may finish our logging context before the task finishes. There's no reason to not `await` the task, so let's do that. Signed-off-by:
Sean Quah <seanq@matrix.org>
-
- Jun 16, 2022
-
-
Erik Johnston authored
-
reivilibre authored
-
Patrick Cloke authored
Pull out `twitter:` meta tags when generating a preview and use it to augment any `og:` meta tags. Prefers Open Graph information over Twitter card information.
-
reivilibre authored
-
Richard van der Hoff authored
If no database is configured explicitly, use sqlite. This means that you don't have to pass any variables into the image.
-
Jacek Kuśnierz authored
Co-authored-by:
David Robertson <david.m.robertson1@gmail.com>
-
reivilibre authored
-
- Jun 15, 2022
-
-
Richard van der Hoff authored
* Add auth events to events used in tests * Move some event auth checks out to a different method Some of the event auth checks apply to an event's auth_events, rather than the state at the event - which means they can play no part in state resolution. Move them out to a separate method. * Rename check_auth_rules_for_event Now it only checks the state-dependent auth rules, it needs a better name.
-
Shay authored
-
Sean Quah authored
Signed-off-by:
Sean Quah <seanq@element.io>
-
Erik Johnston authored
-
Hannes Lerchl authored
-
reivilibre authored
-
Erik Johnston authored
-
David Robertson authored
Co-authored-by:
Patrick Cloke <clokep@users.noreply.github.com>
-
Erik Johnston authored
Fixes #11887 hopefully. The core change here is that `event_push_summary` now holds a summary of counts up until a much more recent point, meaning that the range of rows we need to count in `event_push_actions` is much smaller. This needs two major changes: 1. When we get a receipt we need to recalculate `event_push_summary` rather than just delete it 2. The logic for deleting `event_push_actions` is now divorced from calculating `event_push_summary`. In future it would be good to calculate `event_push_summary` while we persist a new event (it should just be a case of adding one to the relevant rows in `event_push_summary`), as that will further simplify the get counts logic and remove the need for us to periodically update `event_push_summary` in a background job.
-
Erik Johnston authored
-
reivilibre authored
-
reivilibre authored
-
David Robertson authored
-
reivilibre authored
Fix a long-standing bug which meant that rate limiting was not restrictive enough in some cases. (#13018)
-
Brendan Abolivier authored
-
Richard van der Hoff authored
* Remove redundant references to `event_edges.room_id` We don't need to care about the room_id here, because we are already checking the event id. * Clean up the event_edges table We make a number of changes to `event_edges`: * We give the `room_id` and `is_state` columns defaults (null and false respectively) so that we can stop populating them. * We drop any rows that have `is_state` set true - they should no longer exist. * We drop any rows that do not exist in `events` - these should not exist either. * We drop the old unique constraint on all the colums, which wasn't much use. * We create a new unique index on `(event_id, prev_event_id)`. * We add a foreign key constraint to `events`. These happen rather differently depending on whether we are on Postgres or SQLite. For SQLite, we just rebuild the whole table, copying only the rows we want to keep. For Postgres, we try to do things in the background as much as possible. * Stop populating `event_edges.room_id` and `is_state` We can just rely on the defaults.
-
David Robertson authored
-
- Jun 14, 2022
-
-
Patrick Cloke authored
-
Patrick Cloke authored
-
reivilibre authored
-
David Robertson authored
* Rename test_fedclient to match its source file * Require at least one destination to be truthy * Explicitly validate user ID in profile endpoint GETs Co-authored-by:
Patrick Cloke <clokep@users.noreply.github.com>
-