23eed4f72a
Bump serde from 1.0.203 to 1.0.204 ( #17409 )
2024-07-08 15:24:21 +01:00
4721177241
Bump mypy-zope from 1.0.4 to 1.0.5 ( #17414 )
2024-07-08 15:24:11 +01:00
7879f288df
Bump pydantic from 2.7.1 to 2.8.2 ( #17415 )
2024-07-08 15:24:01 +01:00
ccbd619b43
Declare support for Matrix 1.11 ( #17403 )
...
Previous: https://github.com/element-hq/synapse/pull/17082
Fixes https://github.com/element-hq/synapse/issues/17402
See https://github.com/element-hq/synapse/issues/17402 for context
**Blocked on https://github.com/element-hq/synapse/pull/17388 **
(required for spec compliance)
2024-07-08 07:37:28 -06:00
c896030f67
MSC3861: allow overriding the introspection endpoint ( #17406 )
...
This makes it easier to go through an internal endpoint instead of the
public facing URL when introspecting tokens, reducing latency.
2024-07-08 14:08:11 +02:00
4d7e53707c
Bump certifi from 2023.7.22 to 2024.7.4 ( #17404 )
2024-07-08 10:32:09 +01:00
cf69f8d59b
Support MSC3916 by adding a federation /thumbnail endpoint and authenticated `_matrix/client/v1/media/thumbnail` endpoint ( #17388 )
...
[MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916 )
added the endpoints `_matrix/federation/v1/media/thumbnail` and the
authenticated `_matrix/client/v1/media/thumbnail`.
This PR implements those endpoints, along with stabilizing
`_matrix/client/v1/media/config` and
`_matrix/client/v1/media/preview_url`.
Complement tests are at
https://github.com/matrix-org/complement/pull/728
2024-07-08 10:11:20 +01:00
20de685a4b
Bump ruff from 0.3.7 to 0.5.0 ( #17381 )
2024-07-05 12:35:57 +00:00
8e9e6f1a0a
Allow enabling sliding sync per-user ( #17393 )
...
Based on #17392
2024-07-05 13:04:27 +01:00
57538eb4d9
Finish up work to allow per-user feature flags ( #17392 )
...
Follows on from @H-Shay's great work at
https://github.com/matrix-org/synapse/pull/15344 and MSC4026.
Also enables its use for MSC3881, mainly as an easy but concrete example
of how to use it.
2024-07-05 13:02:35 +01:00
45b35f8eae
Fix links to MSC3916 ( #17397 )
2024-07-05 12:00:19 +01:00
2ec257d608
Upon deactivation, forget all of the user's rooms ( #17400 )
...
This can help ensure that the rooms are eventually purged if the other
local users also forget them. Synapse already clears some of the room
information as part of the `_background_remove_left_rooms` background
task, but this doesn't catch `events`, `event_json`, etc.
2024-07-05 11:56:52 +01:00
daeaeb2a7b
Fix links in README ( #17379 )
...
I don't think this warrants a changelog?
### Pull Request Checklist
<!-- Please read
https://element-hq.github.io/synapse/latest/development/contributing_guide.html
before submitting your pull request -->
* [x] Pull request is based on the develop branch
* [x] Pull request includes a [changelog
file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog ).
The entry should:
- Be a short description of your change which makes sense to users.
"Fixed a bug that prevented receiving messages from other servers."
instead of "Moved X method from `EventStore` to `EventWorkerStore`.".
- Use markdown where necessary, mostly for `code blocks`.
- End with either a period (.) or an exclamation mark (!).
- Start with a capital letter.
- Feel free to credit yourself, by adding a sentence "Contributed by
@github_username." or "Contributed by [Your Name]." to the end of the
entry.
* [ ] [Code
style](https://element-hq.github.io/synapse/latest/code_style.html ) is
correct
(run the
[linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters ))
2024-07-05 10:34:02 +00:00
7786ae7e1c
Make the release script create a release branch for Complement as well ( #17318 )
2024-07-05 09:07:45 +02:00
22aeb78b77
Add `rooms.required_state` to Sliding Sync `/sync` ( #17342 )
...
Also handles excluding rooms with partial state when people are asking for room membership events unless it's `$LAZY` room membership.
2024-07-04 12:25:36 -05:00
a9d2e40ea4
Changelog entries only get merged if they have the same content and extension ( #17399 )
...
Changelog entries only get merged if they have the same content and
extension
See
https://github.com/element-hq/synapse/pull/17301#discussion_r1665387218
2024-07-04 17:21:25 +01:00
0c4f7a3d16
Merge branch 'master' into develop
2024-07-03 10:19:23 -06:00
75b788f49f
1.110.0
2024-07-03 09:09:29 -06:00
7be03d854b
Add `room_types`/`not_room_types` filtering to Sliding Sync `/sync` ( #17337 )
...
Based on
[MSC3575](https://github.com/matrix-org/matrix-spec-proposals/pull/3575 ):
Sliding Sync
2024-07-02 12:46:27 -05:00
fa91655805
Return some room data in Sliding Sync `/sync` ( #17320 )
...
- Timeline events
- Stripped `invite_state`
Based on [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/pull/3575 ): Sliding Sync
2024-07-02 11:07:05 -05:00
0d2b75cf92
Merge branch 'release-v1.110' into develop
2024-07-02 09:53:32 -06:00
ccce858c4a
1.110.0rc3
2024-07-02 08:29:34 -06:00
99c107920d
Merge remote-tracking branch 'origin/release-v1.110' into develop
2024-07-02 15:12:36 +01:00
1609855ff8
Limit size of presence EDUs ( #17371 )
...
Otherwise they are unbounded.
---------
Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
2024-07-02 14:07:11 +01:00
8f890447b0
Support MSC3916 by adding `_matrix/client/v1/media/download` endpoint ( #17365 )
2024-07-02 14:07:04 +01:00
b905ae27ca
Fix regression when bounding future tokens ( #17391 )
...
Fix bug added in #17386 , where we accidentally used `room_key` for the
receipts stream. See first commit.
Reviewable commit-by-commit
2024-07-02 14:06:36 +01:00
1ce59d7ba0
Fix sync waiting for an invalid token from the "future" ( #17386 )
...
Fixes https://github.com/element-hq/synapse/issues/17274 , hopefully.
Basically, old versions of Synapse could advance streams without
persisting anything in the DB (fixed in #17229 ). On restart those
updates would get lost, and so the position of the stream would revert
to an older position. If this happened across an upgrade to a later
Synapse version which included #17215 , then sync could get blocked
indefinitely (until the stream advanced to the position in the token).
We fix this by bounding the stream positions we'll wait for to the
maximum position of the underlying stream ID generator.
2024-07-02 12:40:03 +01:00
b3b793786c
Fix sync waiting for an invalid token from the "future" ( #17386 )
...
Fixes https://github.com/element-hq/synapse/issues/17274 , hopefully.
Basically, old versions of Synapse could advance streams without
persisting anything in the DB (fixed in #17229 ). On restart those
updates would get lost, and so the position of the stream would revert
to an older position. If this happened across an upgrade to a later
Synapse version which included #17215 , then sync could get blocked
indefinitely (until the stream advanced to the position in the token).
We fix this by bounding the stream positions we'll wait for to the
maximum position of the underlying stream ID generator.
2024-07-02 12:39:49 +01:00
9c8f1a6d41
Fix building debian packages on non-clean checkouts ( #17390 )
...
If we leave the `.so` in place it causes the tests to fail, as it gets
picked up (instead of the newly built .so) and so fails with mismatched
GLIBC errors.
2024-07-02 12:39:32 +01:00
5b5280e3e5
Fix building debian packages for sid ( #17389 )
...
Sid now defaults to python3.12, and our pinned version of cffi (1.5.1)
does not have wheels for 3.12. This installing cffi to fail as we did
not have the correct libs installed to build from source.
2024-07-02 12:38:29 +01:00
635e3927d2
Bump types-setuptools from 69.5.0.20240423 to 70.1.0.20240627 ( #17380 )
2024-07-01 17:46:58 +01:00
a1b8897668
Bump serde_json from 1.0.117 to 1.0.119 ( #17385 )
2024-07-01 13:42:37 +01:00
76b9f14c0a
Bump log from 0.4.21 to 0.4.22 ( #17384 )
2024-07-01 13:42:00 +01:00
1eccbfb82f
Bump cryptography from 42.0.7 to 42.0.8 ( #17382 )
2024-07-01 13:41:48 +01:00
2f5a77efae
Limit size of presence EDUs ( #17371 )
...
Otherwise they are unbounded.
---------
Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
2024-07-01 12:48:36 +01:00
b11f5c984b
Clarify `url_preview_url_blacklist` is a usability feature ( #17356 )
2024-06-28 14:39:54 +01:00
27756c9fdf
Use rstcheck to "lint" the README ( #17367 )
...
Follow up to https://github.com/element-hq/synapse/pull/17363 , so we can
detect issues with the RST file early on.
### Pull Request Checklist
<!-- Please read
https://element-hq.github.io/synapse/latest/development/contributing_guide.html
before submitting your pull request -->
* [x] Pull request is based on the develop branch
* [x] Pull request includes a [changelog
file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog ).
The entry should:
- Be a short description of your change which makes sense to users.
"Fixed a bug that prevented receiving messages from other servers."
instead of "Moved X method from `EventStore` to `EventWorkerStore`.".
- Use markdown where necessary, mostly for `code blocks`.
- End with either a period (.) or an exclamation mark (!).
- Start with a capital letter.
- Feel free to credit yourself, by adding a sentence "Contributed by
@github_username." or "Contributed by [Your Name]." to the end of the
entry.
* [x] [Code
style](https://element-hq.github.io/synapse/latest/code_style.html ) is
correct
(run the
[linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters ))
2024-06-27 13:36:08 +02:00
cc5e5893fe
Handle multiple rows device inbox ( #17362 )
...
Fix bug where we don't get new to-device from remote if they resent a
message we've already persisted and have recorded in the DB twice.
`device_federation_inbox` table doesn't have a unique index, and so we
can race and store an entry in there twice. If we do so then
`simple_select_one_txn` will throw an error due to the query returning
more than one row. We should add an unique index, but it doesn't really
matter so lets just handle the case of multiple rows correctly for now.
2024-06-27 11:04:31 +01:00
7c169f4d2c
Merge branch 'release-v1.110' into develop
2024-06-26 19:00:51 +02:00
f75da9cc53
1.110.0rc2
2024-06-26 18:14:57 +02:00
75c19bf57a
Fix uploading packages to PyPi ( #17363 )
...
As per
https://github.com/sphinx-doc/sphinx/issues/3921#issuecomment-315581557 ,
we need double underscores.
Running `rst2html README.rst > /dev/null` found some more warnings.
2024-06-26 18:14:29 +02:00
b924a8e1a9
Fix uploading packages to PyPi ( #17363 )
...
As per
https://github.com/sphinx-doc/sphinx/issues/3921#issuecomment-315581557 ,
we need double underscores.
Running `rst2html README.rst > /dev/null` found some more warnings.
2024-06-26 18:01:39 +02:00
a8dcd686fb
Fix typo
2024-06-26 15:10:49 +02:00
315b8d2032
Update changelog
2024-06-26 14:39:57 +02:00
9f47513458
1.110.0rc1
2024-06-26 14:09:13 +02:00
ef7fbdfebd
Fixes to the table of contents in the README ( #17329 )
2024-06-25 15:20:59 +00:00
9cf0ef9c70
Fix outdated Security Disclosure Policy references ( #17341 )
2024-06-25 15:58:30 +01:00
a023538822
Re-introduce federation /download endpoint ( #17350 )
2024-06-25 14:35:37 +00:00
f79dbd0f61
Fix refreshable_access_token_lifetime typo ( #17357 )
...
Simple typo in the docs
2024-06-25 12:07:13 +01:00
c89fea3fd1
Limit amount of replication we send ( #17358 )
...
Fixes up #17333 , where we failed to actually send less data (the
`DISTINCT` didn't work due to `stream_id` being different).
We fix this by making it so that every device list outbound poke for a
given user ID has the same stream ID. We can't change the query to only
return e.g. max stream ID as the receivers look up the destinations to
send to by doing `SELECT WHERE stream_id = ?`
2024-06-25 11:17:39 +01:00
dependabot[bot]