-
Notifications
You must be signed in to change notification settings - Fork 114
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
msg.say()返回no id报错(然而可正常发送文本消息,但不能连续发送) #58
Comments
It's great to see you are trying to run Puppet XP with Token Gateway! I'd like to link this issue to: Please keep updated to let us know your progress, thank you very much! |
We have published an NPM version of Wechaty Token Gateway: I'd like to suggest that you use the below command and let me know whether it works for you or not: $ npm install -g [email protected] wechaty-puppet-xp
$ wechaty gateway --puppet wechaty-puppet-xp |
我已经试过了NPM wechaty gateway的方式,虽然这确实带来很大的便利性,但是配合python-wechaty问题依然:1)发送文本消息会报错 no id,然而消息可以发送,只是不能连续发送;2)发送filebox,会报错 no url。【为方便阅读,我把详细的报错信息放在最后】我现在有点怀疑是不是python-wachaty这边的bug? 另外,也许值得一提的是,作为本地gateway服务,还是需要在启动wechaty gateway前设定WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=true 以下为no id 和 no url的详细报错信息python-wechaty 配合 puppet-xp gateway本地服务,文本消息报错 no id: 服务窗口:
python-wechaty程序窗口:
python-wechaty 配合 puppet-xp gateway本地服务,filebox消息报错 no url: 服务窗口:
python-wechaty程序:
|
This is because Python Wechaty does not support TLS yet.
To confirm that, you can try to use the TypeScript version of the Wechaty to see if the same functions work as expected or not:
|
经过尝试,TS version下(我使用的是https://github.com/wechaty/getting-started),发送文本消息没有 no id 报错。
另外,不知道为什么,如果我仅是set WECHATY_PUPPET=wechaty-puppet-service,则TS wechaty连接不上puppetgateway,会提示timeout,我最终set WECHATY_PUPPET_SERVICE_ENDPOINT=127.0.0.1:8080 才能连接上,不知道是否有关系…… |
The full output of the command |
我尝试在运行 wechaty gateway --puppet wechaty-puppet-xp 前先 set WECHATY_LOG=verbose,这回空置一段时间后启动watchdog会导致wechaty退出,gateway还正常。 完整的gateway-puppet-xp verbose log输出如下:
wechaty那边:
|
我也遇到没有办法发图片~ not url。请问你的解决了吗? |
请问一下,这个问题解决了没,现在对接pythonwechaty可以发送图片了没? |
你可以用最新版的puppet-xp试试看,python-wechaty搭配padlocal是可以正常使用filebox的 |
试过了,xp还是发不了图片 |
不用试了。应该是py库没有更新。传参的地方remoteUrl应该是url . 基础库更新了。具体参考golang版本的: wechaty/go-wechaty#106 |
@bigbrother666sh 您好, 另外,也许值得一提的是,作为本地gateway服务,还是需要在启动wechaty gateway前设定WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=true
|
太久远了……现在这个问题还有么?
…On Fri, May 19, 2023 at 10:37 PM SOl0QQ ***@***.***> wrote:
@bigbrother666sh <https://github.com/bigbrother666sh> 您好,
想请问使用的puppet-xp、wechaty、python-wechaty版本是什么样?
------------------------------
另外,也许值得一提的是,作为本地gateway服务,还是需要在启动wechaty
gateway前设定WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=true
不然windows系统下,服务端口是连不上的……
另外在NPM启动xp
gateway服务前,设置的环境变量WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER看起来没有工作,python-wechaty连接时失败,请麻烦指教下
—
Reply to this email directly, view it on GitHub
<#58 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW5NMCNQUP6DASOXE4LR5HDXG6AS3ANCNFSM5L3CNHBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Best Regards!
Zeming(kyle) Zhao
Too many things here we can not make any change with, for example, the
death or the end of the world. But at least, we can do something before
that. And maybe that's the means of liveth.
|
目前已经确认 puppet-xp暂时不支持filebox。大概率目前只能发送纯文本信息
如果使用msg.say ()发送纯文本信息会返回no id 错误:
详细的错误信息:
推测大概率是 puppet-xp和python-wechaty的msg.say()之间还存在什么bug,建议目前使用talker.say () 或者 room.say() 发纯文本不会报错,也可以连续发送
The text was updated successfully, but these errors were encountered: