- May 09, 2022
-
-
Val Lorentz authored
-
Sean Quah authored
There's no guarantee that module callbacks will handle cancellation appropriately. Protect module callbacks with read semantics from cancellation and avoid swallowing `CancelledError`s that arise. Other module callbacks, such as the `on_*` callbacks, are presumed to live on code paths that involve writes and aren't cancellation-friendly. These module callbacks have been left alone. Signed-off-by:
Sean Quah <seanq@element.io>
-
David Robertson authored
-
Sean Quah authored
#12587 has fallen on the wrong side of the release cutoff to the rest of the related PRs. Signed-off-by:
Sean Quah <seanq@element.io>
-
David Robertson authored
-
Erik Johnston authored
Fixes #12669
-
Sheogorath authored
-
Eric Eastwood authored
-
David Robertson authored
-
- May 07, 2022
-
-
David Robertson authored
* Move `pympler` back into the `all` extras Undoes a change I made in #12381. I can't fully remember my reasoning, but this changed the contents of the debian packages in a backwards incompatible way. We're not aware of anyone who's been bitten by this, but we still want to fix it. To the reviewer: please be convinced that the debian packages will still contain pympler after this change. * Debian changelog entry to keep the linter happy
-
David Robertson authored
-
- May 06, 2022
-
-
Erik Johnston authored
-
David Robertson authored
-
reivilibre authored
Add the `notify_appservices_from_worker` configuration option (superseding `notify_appservices`) to allow a generic worker to be designated as the worker to send traffic to Application Services. (#12452)
-
- May 05, 2022
-
-
Andrew Morgan authored
-
DeepBlueV7.X authored
Signed-off-by:
Nicolas Werner <nicolas.werner@hotmail.de>
-
Andrew Morgan authored
-
Andrew Morgan authored
-
Andrew Morgan authored
-
Andrew Morgan authored
Co-authored-by:
Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
-
Šimon Brandner authored
-
reivilibre authored
-
Henry authored
Update the "Build docker images" GitHub Actions workflow to use `docker/metadata-action` to generate docker image tags, instead of a custom shell script. Signed-off-by:
Henry <97804910+henryclw@users.noreply.github.com>
-
Šimon Brandner authored
-
Patrick Cloke authored
Fixes a regression from 8b309adb (#11660) and b65acead (#11752) where events which themselves were an edit or an annotation could have bundled aggregations calculated, which is not allowed.
-
Patrick Cloke authored
The last usage was removed in 5a1dd297 (#8059).
-
Will Hunt authored
-
Erik Johnston authored
-
- May 04, 2022
-
-
Will Hunt authored
* Add mau_appservice_trial_days * Add a test * Tweaks * changelog * Ensure we sync after the delay * Fix types * Add config statement * Fix test * Reinstate logging that got removed * Fix feature name
-
Patrick Cloke authored
getClientIP was deprecated in Twisted 18.4.0, which also added getClientAddress. The Synapse minimum version for Twisted is currently 18.9.0, so all supported versions have the new API.
-
Šimon Brandner authored
* Changes hidden read receipts to be a separate receipt type (instead of a field on `m.read`). * Updates the `/receipts` endpoint to accept `m.fully_read`.
-
Andrew Morgan authored
-
Patrick Cloke authored
* `m.login.jwt`, which was never specced and has been deprecated since Synapse 1.16.0. (`org.matrix.login.jwt` can be used instead.) * `uk.half-shot.msc2778.login.application_service`, which was stabilized as part of the Matrix spec v1.2 release.
-
Sean Quah authored
Don't log stack traces for cancelled requests and use a custom HTTP status code of 499. Signed-off-by:
Sean Quah <seanq@element.io>
-
Patrick Cloke authored
The `latest_event` field of the bundled aggregations for `m.thread` relations did not include bundled aggregations itself. This resulted in clients needing to immediately request the event from the server (and thus making it useless that the latest event itself was serialized instead of just including an event ID).
-
andrew do authored
-
Richard van der Hoff authored
Fixes a couple of formatting errors which were introduced in #12475.
-
- May 03, 2022
-
-
Richard van der Hoff authored
I've seen a few errors which can only plausibly be explained by the calculated event id for an event being different from the ID of the event in the database. It should be cheap to check this, so let's do so and raise an exception.
-
David Robertson authored
-