| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Don't needlessly compute prev_state
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
is wrong.
|
| |
|
|
|
|
| |
resolution algorithm
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
synapse/app/homeserver.py
synapse/state.py
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
context.current_state, rather than based on the auth_events from the event.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
synapse/storage/schema/im.sql
|
| | |
|
|\|
| |
| |
| |
| |
| |
| | |
rejections
Conflicts:
synapse/storage/schema/delta/v12.sql
|
| | |
|
| | |
|
|/
|
|
| |
/query_auth/ so that we don't duplicate events in the response.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
and then immediately calling state_handler.annotate_context_with_state
|
|/
|
|
| |
to call annotate_context_with_state
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
turns out we are actually in
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
`prev_state` is now a list of previous state ids, similiar to
prev_events. `replace_state` now points to what we think was replaced.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
federation_authorization
Conflicts:
synapse/storage/__init__.py
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
from a Pdu key.
|
| |
|
|
|
|
| |
Update tests to catch this case.
|
| |
|
|
|
|
| |
hasn't been incorporated in time for launch.
|
| |
|
| |
|
| |
|
|
|
|
| |
PDU we don't have.
|
|
|
|
| |
than their id's
|
| |
|
|
|