Skip to content
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

room.say()不定时发送消息失败 #65

Open
funky-tiger opened this issue Dec 8, 2020 · 0 comments
Open

room.say()不定时发送消息失败 #65

funky-tiger opened this issue Dec 8, 2020 · 0 comments

Comments

@funky-tiger
Copy link

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:
rm -rf package-lock.json
rm -rf node_modules
npm install
  1. Please search in FAQ List first, and make sure your problem has not been solved before.

  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:
    "wechaty": "^0.50.7",

  • What is your wechaty-puppet-donut version?
    Answer:
    "wechaty-puppet": "^0.32.3",
    "wechaty-puppet-hostie": "^0.10.8"

  • What is your node version? (run node --version)
    Answer:
    node -v
    v14.15.0

  • What os are you using
    Answer:
    windows

2. Describe the bug

  • 机器人会不定时的发不出去消息
  • 通过room.say()方法
  • 会进入到room.say.catch(error => {}) 中

3. To Reproduce

  • 因为只是一个不定时的问题
  • 所以不好重现
  • 本地测试跑没什么问题
  • 线上量大了之后会有几率出现这样的问题

4. Expected behavior

  • 期望API能够稳定一些

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)

{ Error: 13 INTERNAL: TIMEOUT, can not get message callback response, data: {"content":"发送的消息","to_wxid":"23349952018@chatroom"}
2020-12-07 09:12:58:     at Object.exports.createStatusError (/app/node_modules/grpc/src/common.js:91:15)
2020-12-07 09:12:58:     at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1209:28)
2020-12-07 09:12:58:     at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
2020-12-07 09:12:58:     at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
2020-12-07 09:12:58:     at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
2020-12-07 09:12:58:   code: 13,
2020-12-07 09:12:58:   metadata: Metadata { _internal_repr: {}, flags: 0 },
2020-12-07 09:12:58:   details:
2020-12-07 09:12:58:    'TIMEOUT, can not get message callback response, data: {"content":"发送的消息","to_wxid":"23349952018@chatroom"}' }

$ 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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant