Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | s/get_room_version/get_room_version_id/ | Richard van der Hoff | 2020-01-31 | 1 | -1/+1 |
| | | | | | ... to make way for a forthcoming get_room_version which returns a RoomVersion object. | ||||
* | Add more logging around message retention policies support (#6717) | Brendan Abolivier | 2020-01-17 | 1 | -0/+13 |
| | | | So we can debug issues like #6683 more easily | ||||
* | Fix instantiation of message retention purge jobs | Brendan Abolivier | 2020-01-15 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | When figuring out which topological token to start a purge job at, we need to do the following: 1. Figure out a timestamp before which events will be purged 2. Select the first stream ordering after that timestamp 3. Select info about the first event after that stream ordering 4. Build a topological token from that info In some situations (e.g. quiet rooms with a short max_lifetime), there might not be an event after the stream ordering at step 3, therefore we abort the purge with the error `No event found`. To mitigate that, this patch fetches the first event _before_ the stream ordering, instead of after. | ||||
* | Convert federation backfill to async | Richard van der Hoff | 2019-12-11 | 1 | -14/+13 |
| | | | | | | | | | PaginationHandler.get_messages is only called by RoomMessageListRestServlet, which is async. Chase the code path down from there: - FederationHandler.maybe_backfill (and nested try_backfill) - FederationHandler.backfill | ||||
* | Merge branch 'develop' into babolivier/message_retention | Brendan Abolivier | 2019-11-26 | 1 | -2/+4 |
|\ | |||||
| * | Merge branch 'develop' of github.com:matrix-org/synapse into ↵ | Erik Johnston | 2019-11-04 | 1 | -7/+6 |
| |\ | | | | | | | | | | erikj/split_purge_history | ||||
| * \ | Merge branch 'develop' of github.com:matrix-org/synapse into ↵ | Erik Johnston | 2019-10-31 | 1 | -2/+3 |
| |\ \ | | | | | | | | | | | | | erikj/split_purge_history | ||||
| * | | | Split purge API into events vs state | Erik Johnston | 2019-10-30 | 1 | -2/+5 |
| | | | | |||||
* | | | | Lint | Brendan Abolivier | 2019-11-19 | 1 | -11/+6 |
| | | | | |||||
* | | | | Implement per-room message retention policies | Brendan Abolivier | 2019-11-04 | 1 | -0/+111 |
| |_|/ |/| | | |||||
* | | | Update black to 19.10b0 (#6304) | Amber Brown | 2019-11-01 | 1 | -7/+6 |
| |/ |/| | | | * update version of black and also fix the mypy config being overridden | ||||
* | | Port to use state storage | Erik Johnston | 2019-10-30 | 1 | -2/+4 |
|/ | |||||
* | Servlet to purge old rooms (#5845) | Richard van der Hoff | 2019-08-22 | 1 | -0/+17 |
| | |||||
* | Replace returnValue with return (#5736) | Amber Brown | 2019-07-23 | 1 | -8/+6 |
| | |||||
* | Move logging utilities out of the side drawer of util/ and into logging/ (#5606) | Amber Brown | 2019-07-04 | 1 | -1/+1 |
| | |||||
* | Fix /messages on workers when no from param specified. | Erik Johnston | 2019-06-24 | 1 | -3/+1 |
| | | | | | | | If no `from` param is specified we calculate and use the "current token" that inlcuded typing, presence, etc. These are unused during pagination and are not available on workers, so we simply don't calculate them. | ||||
* | Run Black. (#5482) | Amber Brown | 2019-06-20 | 1 | -38/+30 |
| | |||||
* | Allow client event serialization to be async | Erik Johnston | 2019-05-14 | 1 | -9/+13 |
| | |||||
* | Log tracebacks correctly | Erik Johnston | 2019-02-25 | 1 | -1/+5 |
| | |||||
* | Merge pull request #4263 from rkfg/develop | Erik Johnston | 2019-02-21 | 1 | -1/+1 |
|\ | | | | | Prevent crash on pagination. | ||||
| * | Prevent crash on pagination. | rkfg | 2018-12-06 | 1 | -1/+1 |
| | | |||||
* | | fix NPE in /messages by checking if all events were filtered out (#4330) | Matthew Hodgson | 2019-01-02 | 1 | -10/+11 |
|/ | |||||
* | Refactor state group lookup to reduce DB hits (#4011) | Erik Johnston | 2018-10-25 | 1 | -8/+7 |
| | | | | | | | | Currently when fetching state groups from the data store we make two hits two the database: once for members and once for non-members (unless request is filtered to one or the other). This adds needless load to the datbase, so this PR refactors the lookup to make only a single database hit. | ||||
* | don't filter membership events based on history visibility (#3874) | Matthew Hodgson | 2018-09-14 | 1 | -8/+1 |
| | | | | | | | | don't filter membership events based on history visibility as we will already have filtered the messages in the timeline, and state events are always visible. and because @erikjohnston said so. | ||||
* | lazyload aware /messages (#3589) | Matthew Hodgson | 2018-08-16 | 1 | -1/+34 |
| | |||||
* | Rename async to async_helpers because `async` is a keyword on Python 3.7 (#3678) | Amber Brown | 2018-08-10 | 1 | -1/+1 |
| | |||||
* | Move PaginationHandler to its own file | Erik Johnston | 2018-07-20 | 1 | -0/+265 |