‐‐‐ Original Message ‐‐‐
On Saturday, January 30, 2021 11:50 AM, Bischoop wrote:
> Got problem with responding for Ping,
> tried so many ways to response
> and always end up with time out or other error.
> This time:
>
Is it possible to share your final Ping answer with the list?
I've
‐‐‐ Original Message ‐‐‐
On Saturday, January 30, 2021 11:50 AM, Bischoop wrote:
> Got problem with responding for Ping, tried so many ways to response
> and always end up with time out or other error. This time:
>
Is it possible to share your final Ping answer?
I've had a long term Fl
On 04/02/2021 07.07, Dennis Lee Bieber wrote:
> On Tue, 02 Feb 2021 20:26:34 -0500, Random832
> declaimed the following:
>
>
>> 1. It looks like you're forgetting to send \n\r
>
> Isn't the convention \r\n -- from the days of teletype, when the return
> took longer to complete than the
On Sat, Jan 30, 2021, at 11:50, Bischoop wrote:
>
> Got problem with responding for Ping, tried so many ways to response
> and always end up with time out or other error. This time:
1. It looks like you're forgetting to send \n\r
2. i'm not sure if the server ping is guaranteed to have : characte
On 30Jan2021 16:50, Bischoop wrote:
>Got problem with responding for Ping, tried so many ways to response
>and always end up with time out or other error. This time:
>
>ERROR :(Ping timeout: 264 seconds)
>Traceback (most recent call last):
>s.send(bytes('PONG ' + data.split()[1], 'UTF-8'))
>Br
Got problem with responding for Ping, tried so many ways to response
and always end up with time out or other error. This time:
ERROR :(Ping timeout: 264 seconds)
Traceback (most recent call last):
s.send(bytes('PONG ' + data.split()[1], 'UTF-8'))
BrokenPipeError: [Errno 32] Broken pipe
wh
