notebook goes into send loop when readline returns ""
Opened this issue · 11 comments
How can I reproduce the issue?
That is a very good question /shrug
In that case we can probably close this issue, can't we?
If you consider that behaviour intentional, then yes, otherwise it is solved by one if clause after the readline
Did this happen to you and you just don't know how to reproduce it, or is this just hypothetical and you don't know whether this can happen in practice?
According to my wireshark it happens, my guess it is related to a client socket shutdown, I did not find the time to investigate
Saw this and took a quick look..
If you close the client connection ch.readline() will always return an empty string -- however, any subsequent call to send results in an exception Broken pipe which ends the process.. so no looping. Where did you get the wireshark capture?
On my local machine, with the service running in its normal docker container
but who/what was connecting to the service?
No checker function caused this looping when I tested it.. just exploit throws an error since it is not yet implemented
but who/what was connecting to the service?
I think it happened in connections made from the dotnet checker, but not always 🤔