某次心跳超时以后，收不到任何消息

[iguxiaobei]

Important：Please file the issue follow the template, or we won't help you to solve the problem.

0. Report Issue Guide

1. Please run the following command and check whether the problem has been fixed：

npm install wechaty-puppet-padlus@next

2. Please search in the issue first, and make sure your problem had not been reported before

1. Versions

• What is your wechaty version?
  Answer: 0.48.1

• What is your wechaty-puppet-padplus version?
  Answer: 0.7.39

• What is your node version? (run node --version)
  Answer: 10.15.0

• What os are you using
  Answer:Linux

2. Describe the bug

Give a clear and concise description of what the bug is.

3. To Reproduce

This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.

Steps to reproduce the behavior:

1. run '...'
2. ...
3. ...

4. Expected behavior

Give a clear and concise description of what you expected to happen.

5. Actual behavior

If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.

6. Full Output Logs

Set env WECHATY_LOG=silly in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)

We need full log instead of log screenshot or log fragments!

11:43:23 INFO Message Lisener {"domain":null,"_events":{},"_eventsCount":0,"id":"6019732546251432394","payload":{"id":"6019732546251432394","timestamp":1598845402110,"type":15,"filename":"6019732546251432394.mp4","fromId":"wxid_sk8is77hoecy22","mentionIdList":[],"roomId":"19026912286@chatroom","text":"<?xml version=\"1.0\"?>\n<msg>\n\t<videomsg aeskey=\"11e79fbc79018dd628cfaf0a91ee252a\" cdnthumbaeskey=\"11e79fbc79018dd628cfaf0a91ee252a\" cdnvideourl=\"306d02010004663064020100020432ecce1902032f4dc60204db394cd202045f4c71d9043f617570766964656f5f323965653630336330303966333630625f313539383834353339375f32303038333131313433313639393031353363686174726f6f6d0204010400040201000400\" cdnthumburl=\"306d02010004663064020100020432ecce1902032f4dc60204db394cd202045f4c71d9043f617570766964656f5f323965653630336330303966333630625f313539383834353339375f32303038333131313433313639393031353363686174726f6f6d0204010400040201000400\" length=\"1030147\" playlength=\"8\" cdnthumblength=\"12242\" cdnthumbwidth=\"290\" cdnthumbheight=\"512\" fromusername=\"wxid_sk8is77hoecy22\" md5=\"a4abd518c6d0d064effc7bb41526f1a8\" newmd5=\"2c44be471e0475d50270af110e280b18\" isad=\"0\" />\n</msg>\n","toId":"wxid_gj7au4xbtsgw22"}}
11:43:23 WARN Message mention() DEPRECATED. use mentionList() instead.
11:43:25 INFO S3Manager Uploading file to S3: 4979947670246369905_wxid_gj7au4xbtsgw22_1598845404984_.mp4
11:43:29 INFO ConfigManager receive maintain mode heartbeat.
11:44:25 ERR GRPC_GATEWAY ApiType: HEARTBEAT request timeout, traceId: b39e7e4b-64e6-4113-b3d2-97b4cbe82b28
11:44:25 ERR GRPC_GATEWAY can not get heartbeat from grpc server
11:44:25 INFO PadplusManager ready to restart due to receive event: reconnect
11:44:29 INFO ConfigManager receive maintain mode heartbeat.
11:44:56 ERR GRPC_GATEWAY ApiType: INIT request timeout, traceId: aceb9833-1021-4b6c-bc16-9a26d737f9c0
11:44:56 ERR PadplusUser can not get callback result of INIT
11:45:29 INFO ConfigManager receive maintain mode heartbeat.
11:46:29 INFO ConfigManager receive maintain mode heartbeat.
11:47:29 INFO ConfigManager receive maintain mode heartbeat.
11:48:25 ERR GRPC_GATEWAY ApiType: GET_MESSAGE_MEDIA request timeout, traceId: ba031dc5-78b8-4798-af5f-98d2168ca8e4
11:48:25 ERR Bot onMessage:  Save message failed:
Error: can not get callback result of GET_MESSAGE_MEDIA
    at PadplusMessage.<anonymous> (/xiaoju-bot/node_modules/wechaty-puppet-padplus/dist/src/padplus-manager/api-request/message.js:196:23)
    at Generator.next (<anonymous>)
    at fulfilled (/xiaoju-bot/node_modules/wechaty-puppet-padplus/dist/src/padplus-manager/api-request/message.js:5:58)
11:48:29 INFO ConfigManager receive maintain mode heartbeat.

$ WECHATY_LOG=silly node yourbot.js

Question: Paste your FULL(DO NOT ONLY PROVIDE FRAGMENTS) log messages
Answer:

7. Additional context

Add any other context about the problem here.

重启程序以后正常。

[bug]