527 Commits (bc1db16086d0718c9c0bb61b32b825ba62049bb0)

Author	SHA1	Message	Date
Richard van der Hoff	617e8a4653	Allow ThirdPartyRules modules to replace event content ... Support returning a new event dict from `check_event_allowed`.	4 years ago
Richard van der Hoff	d9d86c2996	Remove redundant `token_id` parameter to create_event ... this is always the same as requester.access_token_id.	4 years ago
Richard van der Hoff	123711ed19	Move third_party_rules check to event creation time ... Rather than waiting until we handle the event, call the ThirdPartyRules check when we fist create the event.	4 years ago
Patrick Cloke	629a951b49	Move additional tasks to the background worker, part 4 (#8513)	4 years ago
Erik Johnston	b2486f6656	Fix message duplication if something goes wrong after persisting the event (#8476) ... Should fix #3365.	4 years ago
Andrew Morgan	66ac4b1e34	Allow modules to create and send events into rooms (#8479) ... This PR allows Synapse modules making use of the `ModuleApi` to create and send non-membership events into a room. This can useful to have modules send messages, or change power levels in a room etc. Note that they must send event through a user that's already in the room. The non-membership event limitation is currently arbitrary, as it's another chunk of work and not necessary at the moment.	4 years ago
Patrick Cloke	c9c0ad5e20	Remove the deprecated Handlers object (#8494) ... All handlers now available via get_*_handler() methods on the HomeServer.	4 years ago
Richard van der Hoff	903fcd2d35	update wording	4 years ago
Richard van der Hoff	e775b5bb5b	kill off `send_nonmember_event` ... This is now redundant, and we can just call `handle_new_client_event` directly.	4 years ago
Richard van der Hoff	fd0282201e	pull up event.sender assertion	4 years ago
Richard van der Hoff	2ee302d016	Move shadow-ban check down into `handle_new_client_event`.	4 years ago
Richard van der Hoff	b520a1bf5a	De-duplicate duplicate handling ... move the "duplicate state event" handling down into `handle_new_client_event` where it can be shared between multiple call paths.	4 years ago
Richard van der Hoff	f31f8e6319	Remove stream ordering from Metadata dict (#8452) ... There's no need for it to be in the dict as well as the events table. Instead, we store it in a separate attribute in the EventInternalMetadata object, and populate that on load. This means that we can rely on it being correctly populated for any event which has been persited to the database.	4 years ago
Erik Johnston	ac11fcbbb8	Add EventStreamPosition type (#8388) ... The idea is to remove some of the places we pass around `int`, where it can represent one of two things: 1. the position of an event in the stream; or 2. a token that partitions the stream, used as part of the stream tokens. The valid operations are then: 1. did a position happen before or after a token; 2. get all events that happened before or after a token; and 3. get all events between two tokens. (Note that we don't want to allow other operations as we want to change the tokens to be vector clocks rather than simple ints)	4 years ago
Richard van der Hoff	2983049a77	Factor out `_send_dummy_event_for_room` (#8370) ... this makes it possible to use from the manhole, and seems cleaner anyway.	4 years ago
Erik Johnston	04cc249b43	Add experimental support for sharding event persister. Again. (#8294) ... This is *not* ready for production yet. Caveats: 1. We should write some tests... 2. The stream token that we use for events can get stalled at the minimum position of all writers. This means that new events may not be processed and e.g. sent down sync streams if a writer isn't writing or is slow.	4 years ago
Erik Johnston	fe8ed1b46f	Make `StreamToken.room_key` be a `RoomStreamToken` instance. (#8281)	4 years ago
Erik Johnston	5d3e306d9f	Clean up `Notifier.on_new_room_event` code path (#8288) ... The idea here is that we pass the `max_stream_id` to everything, and only use the stream ID of the particular event to figure out *when* the max stream position has caught up to the event and we can notify people about it. This is to maintain the distinction between the position of an item in the stream (i.e. event A has stream ID 513) and a token that can be used to partition the stream (i.e. give me all events after stream ID 352). This distinction becomes important when the tokens are more complicated than a single number, which they will be once we start tracking the position of multiple writers in the tokens. The valid operations here are: 1. Is a position before or after a token 2. Fetching all events between two tokens 3. Merging multiple tokens to get the "max", i.e. `C = max(A, B)` means that for all positions P where P is before A *or* before B, then P is before C. Future PR will change the token type to a dedicated type.	4 years ago
Erik Johnston	c9dbee50ae	Fixup pusher pool notifications (#8287) ... `pusher_pool.on_new_notifications` expected a min and max stream ID, however that was not what we were passing in. Instead, let's just pass it the current max stream ID and have it track the last stream ID it got passed. I believe that it mostly worked as we called the function for every event. However, it would break for events that got persisted out of order, i.e, that were persisted but the max stream ID wasn't incremented as not all preceding events had finished persisting, and push for that event would be delayed until another event got pushed to the effected users.	4 years ago
Erik Johnston	dc9dcdbd59	Revert "Fixup pusher pool notifications" ... This reverts commit e7fd336a53.	4 years ago
Erik Johnston	e7fd336a53	Fixup pusher pool notifications	4 years ago
Patrick Cloke	c619253db8	Stop sub-classing object (#8249)	4 years ago
Brendan Abolivier	9f8abdcc38	Revert "Add experimental support for sharding event persister. (#8170)" (#8242) ... * Revert "Add experimental support for sharding event persister. (#8170)" This reverts commit 82c1ee1c22. * Changelog	4 years ago
Erik Johnston	82c1ee1c22	Add experimental support for sharding event persister. (#8170) ... This is *not* ready for production yet. Caveats: 1. We should write some tests... 2. The stream token that we use for events can get stalled at the minimum position of all writers. This means that new events may not be processed and e.g. sent down sync streams if a writer isn't writing or is slow.	4 years ago
Patrick Cloke	da77520cd1	Convert additional databases to async/await part 2 (#8200)	4 years ago
Andrew Morgan	e0d6244beb	Remove unused parameter from, and add safeguard in, get_room_data (#8174) ... Small cleanup PR. * Removed the unused `is_guest` argument * Added a safeguard to a (currently) impossible code path, fixing static checking at the same time.	4 years ago
Patrick Cloke	5099bd68da	Do not allow send_nonmember_event to be called with shadow-banned users. (#8158)	4 years ago
Patrick Cloke	cbd8d83da7	Stop shadow-banned users from sending non-member events. (#8142)	4 years ago
Patrick Cloke	eebf52be06	Be stricter about JSON that is accepted by Synapse (#8106)	4 years ago
Patrick Cloke	f40645e60b	Convert events worker database to async/await. (#8071)	4 years ago
Patrick Cloke	3c01724b33	Fix the return type of send_nonmember_events. (#8112)	4 years ago
Patrick Cloke	25e55d2598	Return the previous stream token if a non-member event is a duplicate. (#8093)	4 years ago
Richard van der Hoff	53834bb9c4	Run `remove_push_actions_from_staging` in foreground (#8081) ... If we got an error persisting an event, we would try to remove the push actions asynchronously, which would lead to a 'Re-starting finished log context' warning. I don't think there's any need for this to be asynchronous.	4 years ago
Erik Johnston	5dd73d029e	Add type hints to handlers.message and events.builder (#8067)	4 years ago
Richard van der Hoff	fcbab08cbd	Add an assertion on prev_events in create_new_client_event (#8041) ... I think this would have caught all the cases in https://github.com/matrix-org/synapse/issues/7642 - and I think a 500 makes more sense here than a 403	4 years ago
Patrick Cloke	d4a7829b12	Convert synapse.api to async/await (#8031)	4 years ago
Erik Johnston	a7bdf98d01	Rename database classes to make some sense (#8033)	4 years ago
Patrick Cloke	d8a9cd8d3e	Remove hacky error handling for inlineDeferreds. (#7950)	4 years ago
Patrick Cloke	cc9bb3dc3f	Convert the message handler to async/await. (#7884)	4 years ago
Patrick Cloke	6fca1b3506	Convert _base, profile, and _receipts handlers to async/await (#7860)	4 years ago
Richard van der Hoff	2ab0b021f1	Generate real events when we reject invites (#7804) ... Fixes #2181. The basic premise is that, when we fail to reject an invite via the remote server, we can generate our own out-of-band leave event and persist it as an outlier, so that we have something to send to the client.	4 years ago
Patrick Cloke	e060bf4462	Convert directory handler to async/await (#7727)	5 years ago
Dagfinn Ilmari Mannsåker	a3f11567d9	Replace all remaining six usage with native Python 3 equivalents (#7704)	5 years ago
Patrick Cloke	bd6dc17221	Replace iteritems/itervalues/iterkeys with native versions. (#7692)	5 years ago
Andrew Morgan	f4e6495b5d	Performance improvements and refactor of Ratelimiter (#7595) ... While working on https://github.com/matrix-org/synapse/issues/5665 I found myself digging into the `Ratelimiter` class and seeing that it was both: * Rather undocumented, and * causing a *lot* of config checks This PR attempts to refactor and comment the `Ratelimiter` class, as well as encourage config file accesses to only be done at instantiation. Best to be reviewed commit-by-commit.	5 years ago
Richard van der Hoff	f4269694ce	Optimise some references to hs.config (#7546) ... These are surprisingly expensive, and we only really need to do them at startup.	5 years ago
Erik Johnston	e5c67d04db	Add option to move event persistence off master (#7517)	5 years ago
Erik Johnston	1531b214fc	Add ability to wait for replication streams (#7542) ... The idea here is that if an instance persists an event via the replication HTTP API it can return before we receive that event over replication, which can lead to races where code assumes that persisting an event immediately updates various caches (e.g. current state of the room). Most of Synapse doesn't hit such races, so we don't do the waiting automagically, instead we do so where necessary to avoid unnecessary delays. We may decide to change our minds here if it turns out there are a lot of subtle races going on. People probably want to look at this commit by commit.	5 years ago
Aaron Raimist	250f3eb991	Omit displayname or avatar_url if they aren't set instead of returning null (#7497) ... Per https://github.com/matrix-org/matrix-doc/issues/1436#issuecomment-410089470 they should be omitted instead of returning null or "". They aren't marked as required in the spec. Fixes https://github.com/matrix-org/synapse/issues/7333 Signed-off-by: Aaron Raimist <aaron@raim.ist>	5 years ago
Erik Johnston	1124111a12	Allow censoring of events to happen on workers. (#7492) ... This is safe as we can now write to cache invalidation stream on workers, and is required for when we move event persistence off master.	5 years ago