cc: @ryanlerch

Hey, @ryanlerch any chance to look into this one?

Just wondering if you have the links to the meeting log that was missing?

also, are you able to reproduce this at all?

there is a staging meetbot in https://matrix.to/#/#fedora-zodbot:fedora.im that you can use to play around with without polluting the actual meeting logs

@man2dev any chance to look at those questions?

I think this issue happens after a !startmeeting

ie, if you pass:

!startmeeting
!topic sometopic
!meetingname somemeetingname

it doesn't handle the 2 further lines...you have to start the meeting, wait, then paste the rest.

I'm guessing likely the result of the async nature of maubot - it uses asycio for all it's interactions with the room. My guess is that causes a race condition where messages can come after !startmeeting but before the start function has finished executing.

This seems tricky to fix, tbh - you could try to scan back through the recent room messages as part of start to see if you missed something, but that seems fragile to me.

Issue Update: Log Formatting and Ordering Changes

Apologies for the delayed response. This issue got lost in my mailing lists, and I only came across it today.

The original issue can be observed at 17:02:08 in the following log:
Meeting Log (2024-09-12)

The issue is no longer reproducible:
Testing Log (2025-02-19)

That said, I did notice that the message formatting and order appear to have changed in the logs.

@man2dev any chance to look at those questions?

I think this issue happens after a !startmeeting

ie, if you pass:

!startmeeting
!topic sometopic
!meetingname somemeetingname

it doesn't handle the 2 further lines...you have to start the meeting, wait, then paste the rest.

Something similar happened in today's FESCo meeting.
See https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-25/fesco.2025-02-25-17.00.log.html:

<@zbyszek:fedora.im> 17:02:58 We have 5, let's start.
<@zbyszek:fedora.im> 17:03:08 !fesco 3364
<@zbyszek:fedora.im> 17:03:08 !topic #3364 F42 Incomplete Changes Report
<@zbyszek:fedora.im> 17:03:24 !fesco 3364
<@zodbot:fedora.im> 17:03:25 ● **Opened:** a week ago by amoloney
<@zodbot:fedora.im> 17:03:25 ● **Last Updated:** an hour ago
<@zodbot:fedora.im> 17:03:25 ● **Assignee:** Not Assigned
<@zodbot:fedora.im> 17:03:25 **fesco #3364** (https://pagure.io/fesco/issue/3364):**F42 Incomplete Changes Report**

The first !fesco 3364 was pasted together with the !topic line and didn't elicit a response.

So, this is fixed? Or still happening?

Perhaps we could re-file this upstream against maubot meeting?

I checked it today on infra meeting and the HTML log seems to be created correctly now https://meetbot.fedoraproject.org/meeting-3_matrix_fedoraproject-org/2026-01-08/infrastructure.2026-01-08-17.00.log.html

Closing this as fixed. Feel free to re-open if you still see the issue.