Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Check the state of prev_events a bit more thoroughly when coming over federation #3456

Merged
merged 9 commits into from
Jun 29, 2018

Conversation

hawkowl
Copy link
Contributor

@hawkowl hawkowl commented Jun 27, 2018

No description provided.

@erikjohnston
Copy link
Member

Hmm. I've just had a thought: a server won't necessarily have permission to fetch state for events (e.g. if the server wasn't in the room at the time and history is private).

I guess in the case where an event points to those prev events then we'll discard the event, but pick it up next time someone sends a message?

@erikjohnston erikjohnston self-assigned this Jun 29, 2018
@erikjohnston erikjohnston removed the request for review from a team June 29, 2018 10:32
@erikjohnston
Copy link
Member

I wonder whether we should drop the requirement that you need to be able to produce the prev_events? Given the server may not actually have permission to view the event?

)
self.assertEqual(self.successResultOf(extrem)[0], "$join:test.serv")

@unittest.DEBUG
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this meant to be left here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

errrr no... but it probably doesn't harm anything for right now :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants