Closed suntong closed 3 years ago
npm install wechaty-puppet-padlus@next
No.
What is your wechaty version? Answer: wechaty@0.48.13
wechaty@0.48.13
What is your wechaty-puppet-padplus version? Answer: wechaty-puppet-padplus@0.7.41
wechaty-puppet-padplus@0.7.41
What is your node version? (run node --version) Answer: v10.21.0
node --version
v10.21.0
What os are you using Answer: Ubuntu 20.04 LTS
Ubuntu 20.04 LTS
GRPC_GATEWAY connect timeout, cannot get anything, the first one being GET_CONTACT_SELF_INFO --
GET_CONTACT_SELF_INFO
Error: can not get callback result of GET_CONTACT_SELF_INFO
Steps to reproduce the behavior:
wechaty-puppet-padplus
GRPC_GATEWAY connect OK.
GRPC_GATEWAY connect will timeout.
Set env WECHATY_LOG=silly in order to set log level to silly.
WECHATY_LOG=silly
Exactly same machine and same code, using a different user will not get into such problem. The differences between the two is mainly,
Also, confirmed that it is puppet-padplus's problem, because if I do
puppet-padplus
WECHATY_PUPPET=wechaty-puppet-puppeteer node ding-dong-bot.js
It works fine for my normal account, which is the one that has a huge WX contact list.
[bug]
Previously all were using cached login.
After I somehow triggered login from my mobile phone again, the connection issue then gone.
0. Report Issue Guide
No.
1. Versions
What is your wechaty version? Answer:
wechaty@0.48.13
What is your wechaty-puppet-padplus version? Answer:
wechaty-puppet-padplus@0.7.41
What is your node version? (run
node --version
) Answer:v10.21.0
What os are you using Answer:
Ubuntu 20.04 LTS
2. Describe the bug
GRPC_GATEWAY connect timeout, cannot get anything, the first one being
GET_CONTACT_SELF_INFO
--Error: can not get callback result of GET_CONTACT_SELF_INFO
3. To Reproduce
Steps to reproduce the behavior:
wechaty-puppet-padplus
4. Expected behavior
GRPC_GATEWAY connect OK.
5. Actual behavior
GRPC_GATEWAY connect will timeout.
6. Full Output Logs
Set env
WECHATY_LOG=silly
in order to set log level to silly.Show Logs
```shell $ WECHATY_LOG=silly node ding-dong-bot.js WECHATY_LOG=silly node index.js 23:26:42 SILL Puppet Config: WECHATY_LOG set level to silly 23:26:42 INFO Config registering process.on("unhandledRejection") for development/debug 23:26:42 VERB Config constructor() 23:26:43 VERB Wechaty constructor() 23:26:43 VERB StateSwitch constructor(Wechaty, "{"log":{"enableTimestamp":true,"logLevel":5,"prefixFilter":{}}}") 23:26:43 VERB StateSwitch constructor(WechatyReady, "{"log":{"enableTimestamp":true,"logLevel":5,"prefixFilter":{}}}") 23:26:43 VERB Wechaty on(scan, listener) registering... listenerCount: 0 23:26:43 VERB Wechaty on(login, listener) registering... listenerCount: 0 23:26:43 VERB Wechaty on(logout, listener) registering... listenerCount: 0 23:26:43 VERB Wechaty on(message, listener) registering... listenerCount: 0 23:26:43 VERB Wechaty on(error, listener) registering... listenerCount: 0 23:26:43 VERB Wechaty on(friendship, listener) registering... listenerCount: 0 23:26:43 VERB Wechaty7. Additional context
Exactly same machine and same code, using a different user will not get into such problem. The differences between the two is mainly,
Also, confirmed that it is
puppet-padplus
's problem, because if I doWECHATY_PUPPET=wechaty-puppet-puppeteer node ding-dong-bot.js
It works fine for my normal account, which is the one that has a huge WX contact list.
[bug]