summary refs log tree commit diff
path: root/webclient/home/home.html (unfollow)
<
Commit message (Collapse)AuthorFilesLines
2019-12-20Backport fixes to sqlite upgrade from develop (#6578)Richard van der Hoff2-1/+10
Only run prepare_database on connection for in-memory databases. Fixes #6569.
2019-12-20Fix exceptions when attempting to backfill (#6576)Richard van der Hoff2-1/+5
Fixes #6575
2019-12-18too many parens v1.7.1 github/release-v1.7.1 release-v1.7.1Richard van der Hoff1-1/+1
2019-12-181.7.1Richard van der Hoff14-15/+25
2019-12-17Fix bug where we added duplicate event IDs as auth_events (#6560)Erik Johnston2-7/+9
2019-12-16Add auth events as per spec. (#6556)Erik Johnston2-67/+35
Previously we tried to be clever and filter out some unnecessary event IDs to keep the auth chain small, but that had some annoying interactions with state res v2 so we stop doing that for now.
2019-12-16Incorporate reviewBrendan Abolivier2-6/+1
2019-12-16Update changelog.d/6553.bugfixBrendan Abolivier1-1/+1
Co-Authored-By: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
2019-12-16LintBrendan Abolivier1-2/+1
2019-12-16Add test caseBrendan Abolivier1-0/+133
2019-12-16Exclude rejected state events when calculating state at backwards extrems ↵Richard van der Hoff2-1/+2
(#6527) This fixes a weird bug where, if you were determined enough, you could end up with a rejected event forming part of the state at a backwards-extremity. Authing that backwards extrem would then lead to us trying to pull the rejected event from the db (with allow_rejected=False), which would fail with a 404.
2019-12-16Persist auth/state events at backwards extremities when we fetch them (#6526)Richard van der Hoff3-165/+83
The main point here is to make sure that the state returned by _get_state_in_room has been authed before we try to use it as state in the room.
2019-12-16sanity-checking for events used in state res (#6531)Richard van der Hoff6-43/+128
When we perform state resolution, check that all of the events involved are in the right room.
2019-12-16Sanity-check room ids in event auth (#6530)Richard van der Hoff2-0/+14
When we do an event auth operation, check that all of the events involved are in the right room.
2019-12-16Check the room_id of events when fetching room state/auth (#6524)Richard van der Hoff2-24/+56
When we request the state/auth_events to populate a backwards extremity (on backfill or in the case of missing events in a transaction push), we should check that the returned events are in the right room rather than blindly using them in the room state or auth chain. Given that _get_events_from_store_or_dest takes a room_id, it seems clear that it should be sanity-checking the room_id of the requested events, so let's do it there.