-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MonitorEventsAsync missing or blocking the last piece of data #576
Comments
Is this repository out of maintenance? I mentioned that the issue has been waiting for a long time and no maintainer has fixed it or replied. Since the version of |
Can you share some more information or a small example? I cannot reproduce it. I tried following:
I immediately receive following events: 1661759715 71670a9b1055fafe787592d95b5062cafa6a0616ce3eb139e3e4fd884c86c320 kill
1661759715 71670a9b1055fafe787592d95b5062cafa6a0616ce3eb139e3e4fd884c86c320 die
1661759715 disconnect
1661759715 71670a9b1055fafe787592d95b5062cafa6a0616ce3eb139e3e4fd884c86c320 destroy |
@13750573877 you have to understand that none of us maintaining the project are full time employees of it. We have a life outside of it. I can't reproduce the problem either so if you could make a simple repo with a simple console app reproducing the problem you are complaining it would be useful for us to try find out what is going on. Blame that there is a problem without enough context is like complain that it is cold in Alaska. |
I can confirm this problem. We also encountered with the same version. |
The problem is in lib, because
Logs from our app:
In log from our app the target service receives |
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。
The text was updated successfully, but these errors were encountered: