You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason the way I tried implementing several does-throw tests for show::response doesn't work (see end of issue for code example). It appears writes to the socket succeed and don't block, even if the socket has been closed from the client side or the client isn't reading. This is possibly due to both sockets being in the same process, as I've been able to trigger the desired behavior with two processes, one running a SHOW server and another being a Netcat instance. This needs further investigation; I've leaving these tests artificially failing for now.
The tests are located in tests/response_tests.cpp and are:
For some reason the way I tried implementing several does-throw tests for
show::response
doesn't work (see end of issue for code example). It appears writes to the socket succeed and don't block, even if the socket has been closed from the client side or the client isn't reading. This is possibly due to both sockets being in the same process, as I've been able to trigger the desired behavior with two processes, one running a SHOW server and another being a Netcat instance. This needs further investigation; I've leaving these tests artificially failing for now.The tests are located in
tests/response_tests.cpp
and are:GracefulClientDisconnectWhileCreating
GracefulClientDisconnectWhileSending
GracefulClientDisconnectWhileDestroying
GracefulConnectionTimeoutWhileCreating
GracefulConnectionTimeoutWhileSending
GracefulConnectionTimeoutWhileDestroying
An example of how I tried to implement the tests:
The text was updated successfully, but these errors were encountered: