MonitorEventsAsync missing or blocking the last piece of data

I found that in versions after 3.125.4 using the MonitorEventsAsync method, the last piece of data is lost (blocked), and it will only output the last piece of data when the monitoring event is triggered next time。

It should be caused by modifying the MonitorEventsAsync method code.

Problematic versions: 3.125.5, 3.125.10

Example:
step one:
docker rm xxxx
output action: die

step two:
docker run xxx
output action: destroy create start

The last piece of data is blocked until the next trigger to get it。