-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WARN PuppetPuppeteer initWatchdogForPuppet() dog.on(reset) last food:inited, timeout:120000 #1439
Comments
I just use https://github.com/lijiarui/wechaty-getting-started and the code can be ran without any problem: $ pwd
/home/zixia/git/wechaty-getting-started
$ cat examples/six-lines-bot.js
const { Wechaty } = require('wechaty') // import { Wechaty } from 'wechaty'
Wechaty.instance() // Global Instance
.on('scan', (qrcode, status) => console.log(`Scan QR Code to login: ${status}\n${qrcode}`))
.on('login', user => console.log(`User ${user} logined`))
.on('message', message => console.log(`Message: ${message}`))
.start()
$ node examples/six-lines-bot.js
00:55:49 INFO Wechaty start() v0.17.71 is starting...
00:55:49 INFO Wechaty initPuppet() using puppet: puppeteer
Scan QR Code to login: 0
https://login.weixin.qq.com/l/wfFWHCi2TQ== Can you try to use that repository and reproduce your error? |
Unfortunately, I followed the wecahty-getting-started as you descriped from scratch, but still having the same 'reset' issue. However it seems that nobody else is having the same problem...So I will try to look for some env issue on my local machine. |
Reopen since I found another person having the same issue running the getting-started repo reference https://github.com/lijiarui/wechaty-getting-started/issues/20 |
Okay, got it. Thanks for reporting and we will go to confirm it later. |
I got the same issue on my Macbook. Everything is OK after the bot being started, but after several minutes, the issue occurs. |
It seems the Wechaty PuppetPuppeteer has this bug for Wechaty v0.15 v0.16 v0.17, and please know that those versions are all not STABLE(please see the release notes), because of v0.15 & v0.17 is the alpha version(see #905), v0.16 is a beta version for Wechaty PuppetPadchat. (see release notes for v0.16) WorkaroundPlease install RoadmapWe are planing to fix this issue not after Wechaty v0.20. |
temp const wechaty = new Wechaty()
wechaty.on('login', () => {
const watchdog = () => {
wechaty.puppet.emit('watchdog', { data: 'any', timeout: 2 * 60 * 1000 })
setTimeout(watchdog, 60 * 1000)
}
watchdog()
}) |
This issue should be fixed on Wechaty v0.17.116 or above. |
Provide Your Network Information
China
Local
Run
npm run doctor
orwechaty run doctor
(for docker user), paste output hereWechaty Doctor
Expected behavior
Should not see the following warning message all the time
'WARN PuppetPuppeteer initWatchdogForPuppet() dog.on(reset) last food:inited, timeout:120000' and the browser(set WECHATY_HEAD=true) should not restart with the reset
Actual behavior
After scaning qrcode to login, the terminal keeps saying 'WARN PuppetPuppeteer initWatchdogForPuppet() dog.on(reset) last food:inited, timeout:120000' and the browser keeps restarting. Although events like 'message' work fine.
Steps to reproduce the behavior (and fixes, if any)
npm --registry https://registry.npm.taobao.org install wechaty
node test.js
test.js file:
Full Output Logs
Paste the full output logs here with
WECHATY_LOG=silly
setThe text was updated successfully, but these errors were encountered: