We try to do a PiTR with mariadb-binlog.

Let us assume we have 2 binary logs:

binlog.000075
binlog.000076

and the point we want to recover to is 16:27:00 which is in binlog #76 (16:25:35 - 16:27:48)

the typical process would be:

1. mariadb-binlog --disable-log-bin --stop-datetime='2025-01-10 16:27:00' binlog.000075 binlog.000076 >/dev/null

And then we get this nasty warning:

WARNING: Did not reach stop datetime '2025-01-10 16:27:00' before end of input

OK. It is just a warning. But it confuses users in a critical operation...

Breakting it down it is cause by binlog #75:

1. mariadb-binlog --disable-log-bin --stop-datetime='2025-01-10 16:27:00' binlog.000076 >/dev/null
2. mariadb-binlog --disable-log-bin --stop-datetime='2025-01-10 16:27:00' binlog.000075 >/dev/null
   WARNING: Did not reach stop datetime '2025-01-10 16:27:00' before end of input

Possibly this was introduced in work for MDEV-35528?