From 0ce85d3d53556e944f46094434a92814077f1eb6 Mon Sep 17 00:00:00 2001
From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Date: Tue, 22 Feb 2022 10:27:55 +0000
Subject: [PATCH] send_join test: Omit create event from `state` (#1193)

As of MSC3706, omitting the create event from `auth_chain` is valid (because it
should also be in `state`). But it definitely *should* be there in `state`.
---
 tests/50federation/30room-join.pl | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tests/50federation/30room-join.pl b/tests/50federation/30room-join.pl
index 931d8b1c0..2cac32c57 100644
--- a/tests/50federation/30room-join.pl
+++ b/tests/50federation/30room-join.pl
@@ -883,14 +883,14 @@ sub assert_is_valid_pdu {
                map { $_->[0] } @{ $event->{auth_events} }
             );
 
-            # filter out the m.room.create event
-            @auth_chain = grep { $_->{type} ne 'm.room.create' } @auth_chain;
+            # filter out the m.room.create event from the state response
+            my @state_events = grep { $_->{type} ne 'm.room.create' } $room->current_state_events;
 
             $req->respond_json(
                # /v1/send_join has an extraneous [200, ...] wrapper (see MSC1802)
                my $response = [ 200, {
                   auth_chain => \@auth_chain,
-                  state      => [ $room->current_state_events ],
+                  state      => \@state_events,
                } ]
             );