Bug #118415 [Warning] [MY-011809] [Server] Cannot replicate to server with server_uuid

Description:
2025-05-03T11:05:42.955275+08:00 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log 
instead: MY-001158 - Got an error reading communication packets
2025-05-03T11:05:13.471363+08:00 148 [ERROR] [MY-011161] [Repl] Semi-sync source failed on net_flush() before waiting for replica reply.
2025-05-03T11:06:14.354229+08:00 3780081 [Warning] [MY-011153] [Repl] Timeout waiting for reply of binlog (file: mysql-bin.021718, pos: 980193251), semi-sync up to file mysql-bin.021718, position 980193251), 
2025-05-03T11:11:52.932128+08:00 3782120 [Warning] [MY-011809] [Server] Cannot replicate to server with server_uuid='b10ca143-23fg-14f0-bcf1-0052314886f1' because the present server has purged required binary 
logs. The connecting server needs to replicate the missing transactions from elsewhere.

How to repeat:
2025-05-03T11:05:42.955275+08:00 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log 
instead: MY-001158 - Got an error reading communication packets
2025-05-03T11:05:13.471363+08:00 148 [ERROR] [MY-011161] [Repl] Semi-sync source failed on net_flush() before waiting for replica reply.
2025-05-03T11:06:14.354229+08:00 3780081 [Warning] [MY-011153] [Repl] Timeout waiting for reply of binlog (file: mysql-bin.021718, pos: 980193251), semi-sync up to file mysql-bin.021718, position 980193251), 
2025-05-03T11:11:52.932128+08:00 3782120 [Warning] [MY-011809] [Server] Cannot replicate to server with server_uuid='b10ca143-23fg-14f0-bcf1-0052314886f1' because the present server has purged required binary 
logs. The connecting server needs to replicate the missing transactions from elsewhere.

What version of MySQL is this?
What happened before this failure?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".