The problem here appears to be that the /state_ids request is racing against the current-state calculation:

  synapse_main | 2022-08-25 16:45:29,290 - synapse.handlers.federation - 1653 - INFO - sync_partial_state_room-0 - Updating current state for !0:host.docker.internal:46871
  synapse_main | 2022-08-25 16:45:29,312 - synapse.http.server - 169 - INFO - GET-13 - <SynapseRequest at 0x7f994cefe370 method='GET' uri='/_matrix/federation/v1/state_ids/%210:host.docker.internal:46871?event_id=%24bO0OjeuzEcRmdWzNWTJLIKtM2MQy_VET2J1-4bayLBg' clientproto='HTTP/1.0' site='8080'> SynapseError: 403 - Host not in room.
  synapse_main | 2022-08-25 16:45:29,314 - synapse.access.http.8080 - 450 - INFO - GET-13 - ::ffff:127.0.0.1 - 8080 - {host.docker.internal:46871} Processed request: 0.003sec/0.001sec (0.002sec, 0.000sec) (0.000sec/0.000sec/1) 53B 403 "GET /_matrix/federation/v1/state_ids/%210:host.docker.internal:46871?event_id=%24bO0OjeuzEcRmdWzNWTJLIKtM2MQy_VET2J1-4bayLBg HTTP/1.0" "Go-http-client/1.1" [0 dbevts]
  synapse_main | 2022-08-25 16:45:29,324 - synapse.handlers.federation - 1658 - INFO - sync_partial_state_room-0 - Clearing partial-state flag for !0:host.docker.internal:46871

We can see that the "updating current state" operation is ongoing as the state_ids request arrives. The same is true for the other failures linked above.

So really this is an artifact of #13288, though I might see if we can hack around it for now.

Uh oh!

Complement test TestPartialStateJoin/CanReceiveEventsWithMissingParentsDuringPartialStateJoin is flaky #13564

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Complement test `TestPartialStateJoin/CanReceiveEventsWithMissingParentsDuringPartialStateJoin` is flaky #13564