This repository has been archived by the owner on Aug 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 74
关于消息响应&Bot退出 #774
Comments
BTMuli
added
bug
Something isn't working
question
Further information is requested
labels
Apr 2, 2022
麻烦在 git bash 中跑,我实在无力在 windows 环境中全量测试和兼容 |
参考 #140 |
用 gitbash 启动报错 |
这两天趁着周末我搬到Ubuntu上面跑好了😂,感觉用windows问题挺多的T_T |
警告应该没关系吧 |
node:events:504
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE: address already in use 127.0.0.1:9934 这个端口是写死的吗?能不能加个配置选项QWQ |
写死的,加不了,本来就不想一个机器跑多个,因为数据库不支持多进程,有多个 qq 可以写在配置文件里 |
Arondight
added
wontfix
This will not be worked on
and removed
question
Further information is requested
labels
Apr 2, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
问题描述
首先是消息响应问题
今天更新后发现对于一些命令的响应异常,有的是没有回应,有的是同一个回应发了两次
好吧,刚刚看了一下,发现可能是被风控的原因,又发了一遍——但实际上之前那条消息是正确发送了的,所以发了两遍实际上
还有一个就是Bot退出的问题,之前我都是采用ctrl+C退出的,然后会有下线通知
这几天更新之后没有发送下线通知了
复现流程
略(
后台日志
No response
运行环境
当前提交
代码状态
The text was updated successfully, but these errors were encountered: