Yuan Gao
From this [blog post](https://blog.csdn.net/lanyang123456/article/details/89288824) > 4.总结 > 如果server端没有启动，client尝试连接时，会收到RST。 > > 连接建立后，如果读端或者写端关闭连接，具体分两种情况： > > 如果读端关闭连接，写端继续写，第一次写，会收到RST，再写，报错broken pipe > 如果写端关闭连接，读端继续读，报错EOF So the problem is probably the server side close the connection first. I...
Here is the log in the hostie server when the connection dropped: ```shell tcp_custom.cc:218] write complete on 029FCC20: error={"created":"@1594210168.896000000","description":"TCP Write failed","file":"d:\a\grpc-node\grpc-node\packages\grpc-native-core\deps\grpc\src\core\lib\iomgr\tcp_uv.cc","file_line":72,"grpc_status":14,"os_error":"message too long"} ``` There are multiple `TCP Write Failed`...
The `TCP Write Failed` with `os_error` is `message too long`, they somehow points to a word [`MTU`](https://en.wikipedia.org/wiki/Maximum_transmission_unit). Then I found some article related to docker `MTU` issues: https://mlohr.com/docker-mtu/ https://medium.com/@sylwit/how-we-spent-a-full-day-figuring-out-a-mtu-issue-with-docker-4d81fdfe2caf When...
Linked [StackOverFlow](https://stackoverflow.com/questions/62829966/what-are-the-causes-for-os-error-message-too-long/62837579) Thanks for [murgatroid99](https://stackoverflow.com/users/159388/murgatroid99)'s comments, another keyword `EMSGSIZE` appears. Below is the original answer: > The string "message too long" is the error message for the error code UV_EMSGSIZE,...
@huan Any progress on your side?
> Maybe we should have a look at `ulimit` for the Docker: > > See: > > * https://docs.oracle.com/cd/E37670_01/E75728/html/ch04s16.html > * https://docs.docker.com/compose/compose-file/#ulimits > > The `userns_mode` / might also desire...
Since the current design for `wechaty-puppet-service` is using a websocket to register the server, how about we add one more parameter when we initialize the connection? I checked the code...
After some investigation, I found that we are trying to find a way to pass the error along the stream to the destination, but actually this is not the best...
I tried to throw error in the error listener, and catch outside the function, but seems like the error listener's running context is different, and the error can not be...