Concurrent DML and REPAIR leads to replication failure

git clone https://github.com/MariaDB/randgen --branch mdev38599 rqg-mdev38599

cd rqg-mdev38599

. ./mdev38599.cmd <basedir>

2026-01-19 21:31:50 7 [ERROR] mysqld: Can't find record in 't'

2026-01-19 21:31:50 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table test.t; Can't find record in 't', Error_code: 1032; handler error HA_ERR

_END_OF_FILE; the event's master log mysql-bin.000001, end_log_pos 0, Gtid 0-1001-83, Internal MariaDB error code: 1032

2026-01-19 21:31:50 7 [Warning] Slave: Can't find record in 't' Error_code: 1032

perl ./run.pl --base-port=17000 --basedir=$basedir --duration=200 --grammar=mdev38599.yy --mysqld=--innodb-lock-wait-timeout=2 --mysqld=--lock-wait-timeout=4 --mysqld=--log-bin --mysqld=--max-statement-time=6 --scenario=Replication --threads=4 --vardir=/dev/shm/var-mdev38599 --seed=1768603409 --nometadata-reload

query_init:

  CREATE TABLE IF NOT EXISTS test.t (a INT) ENGINE=InnoDB ;

query:

  ==FACTOR:2== INSERT INTO test.t VALUES (_int),(_int),(_int),(_int) |

  DELETE FROM test.t ORDER BY a LIMIT _digit

;

thread1:

  REPAIR TABLE test.t;