juzibot / donut-tester

40 stars 4 forks source link

WARN Puppet dogReset() reason: {"data":"onGrpcStreamEvent(EVENT_TYPE_LOGIN)","timeout":60000} #53

Closed tomallv closed 3 years ago

tomallv commented 3 years ago

Today, i instead the padplus token by donut token, just modified the main function (.js file ) follow by the example from https://github.com/juzibot/donut-tester as bellow:

========================================================= const { Wechaty } = require("wechaty") // Wechaty核心包 const config = require("./config") // 配置文件

const onScan = require("./onScan") // 机器人需要扫描二维码时监听回调 const onRoomJoin = require("./onRoomJoin") // 加入房间监听回调 const onMessage = require("./onMessage") // 消息监听回调 const onFriendShip = require("./onFriendShip") // 好友添加监听回调

const token = config.token

// 初始化 const bot = new Wechaty({ puppet: "wechaty-puppet-hostie", puppetOptions: {token,} })

bot .on("scan", onScan) // 机器人需要扫描二维码时监听 .on("room-join", onRoomJoin) // 加入房间监听 .on("message", onMessage(bot)) // 消息监听 .on("friendship", onFriendShip) // 好友添加监听 .start()

On the 1st time to start, it works well. I can login var QRcode, the info of windows client has been login shown on the phone and also received the message from "Bot Setry" on wechat client.

Under this case, i sent several wechat message to bot, it works well. And then i use my ex-wechat account create a room and add bot, sent message in the room via my ex-wechat account, no response on bot. wait about 2-3 mins, the waring "WARN Puppet dogReset() reason: {"data":"onGrpcStreamEvent(EVENT_TYPE_LOGIN)","timeout":60000} " pops up.

i restart bot, got the same issue. So i logout the windows cline from my phone. and restart bot, unfortunately no login qr-code pops up, and get the same waring info as below screenshot:

image

version info: "qrcode-terminal": "^0.12.0", "request": "^2.88.2", "urlencode": "^1.1.0", "wechaty": "^0.51.1", "wechaty-puppet": "^0.32.3",

please help me to check where is wrong? thanks!

su-chang commented 3 years ago

Thank you for your issue, please contact with juzibot and send your token to him. We will check it after that.

tomallv commented 3 years ago

OK, i have contacted with juzibot with offering my donut token, please help to check, thanks a lot!

su-chang commented 3 years ago

If there's no problem any more, please feel free to close it, thank you.

tomallv commented 3 years ago

This issue had been resolved via juzibot, due to the exception during the resource allocation in server side. I will keep one eye on this about one week, if it doesn't occurs again, i will close this.

tomallv commented 3 years ago

This issue was reproduced in this afternoon, and donut token has been sent to juzibot with logs. Under juzibot requests, i set WECHATY_LOG=silly.

tomallv commented 3 years ago

i haven't met this issue in last one week, so close it.

sunshinearea commented 3 years ago

@su-chang @tomallv Hello, I have encountered the same problem. After successful startup login, the bot will automatically drop the line and automatically log in. May I ask how to deal with this problem?

It has been solved. Wechaty@0.50.7, wechaty-pure-Hostie @0.11.0 can be solved