notebook goes into send loop when readline returns ""

[Trolldemorted]

No description provided.

[gehaxelt]

How can I reproduce the issue?

[Trolldemorted]

That is a very good question /shrug

[gehaxelt]

In that case we can probably close this issue, can't we?

[Trolldemorted]

If you consider that behaviour intentional, then yes, otherwise it is solved by one if clause after the readline

[ldruschk]

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?

[Trolldemorted]

According to my wireshark it happens, my guess it is related to a client socket shutdown, I did not find the time to investigate

[sinitax]

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?

[Trolldemorted]

On my local machine, with the service running in its normal docker container

[sinitax]

but who/what was connecting to the service?

[sinitax]

No checker function caused this looping when I tested it.. just exploit throws an error since it is not yet implemented

[Trolldemorted]

but who/what was connecting to the service?

I think it happened in connections made from the dotnet checker, but not always 🤔