Yuan Gao

> please compare these two approaches and tell me which one you like with built-in i18n: #1514 with serperate submenu: #1513 Vote for build-in i18n

Hope this can be implemented soon. This is badly affecting our sticky services deployed with docker. Now we need to add extra configurations and placement for those services, since host...

Thanks for such fast reply. I've looked into the code and found that after the `initWebSocket()` function call, there is no `open` event triggered, seems pretty weird, maybe this is...

Hi @huan how's this issue going?

Shall we add some check around the `reset` inside the `error` listener? We should not `reset` the `wechaty instance` unless we know the error means something really bad and a...

I would assume most errors we encountered recently do not require a system recover, the system is not down. So it would be better to use `log to console` as...

Maybe we need to refer to [this comments](https://github.com/grpc/grpc-node/issues/692#issuecomment-578865204) and do a retry logic for our grpc connection.

> However, I feel that there are other reasons that caused the Write Failed, as I posted above on Apr, as my experience, this issue happens a lot when we...

I finally got a reproduce code: ```ts import { Contact, Wechaty, Room } from 'wechaty'; const bot = new Wechaty({ puppet: 'wechaty-puppet-hostie', puppetOptions: { token: 'a-very-secret-token-that-no-one-knows', }}); const syncContact =...

I found the lower layer error happened in TCP layer ```shell read: error={"created":"@1594209127.281811000","description":"EOF","file":"../deps/grpc/src/core/lib/iomgr/tcp_uv.cc","file_line":106} ... // A lot of write binary data log write complete on 0x10271cf00: error="No Error" TCP 0x10271cf00...