colerar / bikkuri Goto Github PK

10-24T19:23:58.124 - I [nioEventLoopGroup-2-1] [net.mamoe.mirai.internal.utils.Log4jLoggerAdapter] >>> Bot cancelled: Bot closed
10-24T19:23:58.123 - E [main] [net.mamoe.mirai.internal.utils.Log4jLoggerAdapter] >>> null
net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(2188206043), code=235, title=温馨提示, message=当前QQ版本过低，请升级至最新版本后再登录。点击进入下载页面, errorInfo=)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:309)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33)
at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
10-24T19:23:58.127 - I [main] [net.mamoe.mirai.internal.utils.Log4jLoggerAdapter] >>> mirai-console started successfully.

使用TxCaptchaHelper，然后登陆时出现了这个问题

如题

环境：程序每天0点、12点被kill，0点1分、12点1分启动

这个功能确实有用，能在群被封了之后把人重新拉回来

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency org.jetbrains.kotlin.plugin.serialization to v1.9.10
• fix(deps): update dependency dev.inmo:krontab to v2.2.2
• fix(deps): update ktor to v2.3.5 (io.ktor:ktor-utils, io.ktor:ktor-serialization-kotlinx-json, io.ktor:ktor-client-content-negotiation, io.ktor:ktor-client-encoding, io.ktor:ktor-client-okhttp, io.ktor:ktor-client-core)
• chore(deps): update plugin spotless to v6.22.0
• fix(deps): update dependency com.squareup.okio:okio to v3.6.0
• fix(deps): update dependency org.xerial:sqlite-jdbc to v3.43.2.1
• fix(deps): update exposed to v0.44.0 (org.jetbrains.exposed:exposed-java-time, org.jetbrains.exposed:exposed-kotlin-datetime, org.jetbrains.exposed:exposed-jdbc, org.jetbrains.exposed:exposed-dao, org.jetbrains.exposed:exposed-core)
• fix(deps): update mirai to v2.16.0 (net.mamoe:mirai-logging-slf4j-logback, net.mamoe:mirai-logging-slf4j, net.mamoe:mirai-core-utils, net.mamoe:mirai-core-api, net.mamoe:mirai-core)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

ccessfully loaded friend list: 3 in total
06-24T16:38:12.802 - I [DefaultDispatcher-worker-1] [net.mamoe.mirai.Bot] >>> Successfully loaded group list: 5 in total.
06-24T16:38:12.811 - I [DefaultDispatcher-worker-7] [net.mamoe.mirai.Bot] >>> Scheduled key refresh in 23h 55min 0.0s.
06-24T16:38:12.812 - I [DefaultDispatcher-worker-7] [net.mamoe.mirai.Bot] >>> Scheduled refresh login session in 19d 23h 55min 0.0s.
06-24T16:38:12.813 - I [DefaultDispatcher-worker-7] [net.mamoe.mirai.Bot] >>> Syncing friend message history: Success.
06-24T16:38:12.816 - I [DefaultDispatcher-worker-2] [net.mamoe.mirai.Bot] >>> Bot login successful.
06-24T16:38:22.716 - I [DefaultDispatcher-worker-1] [me.hbj.bikkuri.tasks.UpdateGuardList] >>> Successfully connect to live room 91164
06-24T16:41:22.951 - I [nioEventLoopGroup-2-4] [me.hbj.bikkuri.events.MemberRequest] >>> Add MemberJoinRequestEvent to queue: MemberJoinRequestEvent(bot=Bot(2188206043), eventId=1687596082248518, message=大家好，我是清瑶。来自湖北武汉的处女座女一枚~, fromId=647067598, groupId=524795444, groupName=F0FTGの舰长审核群, fromNick=清瑶, invitorId=null)
06-24T16:41:24.383 - I [DefaultDispatcher-worker-2] [me.hbj.bikkuri.tasks.AutoApprove] >>> Accept join request: MemberJoinRequestEvent(bot=Bot(2188206043), eventId=1687596082248518, message=大家好，我是清瑶。来自湖北武汉的处女座女一枚~, fromId=647067598, groupId=524795444, groupName=F0FTGの舰长审核群, fromNick=清瑶, invitorId=null)

机器人能够完成除了说话以外的其他任务，但就是无法说话，用命令什么的也不说话
服务器在美国，查看机器人qq登录状态是手表在线
2.2.0版本

如题，有些人的账号因为一些原因被qq过滤了，而机器人不会搭理那些被过滤的申请，看看有没有办法解决？

不再依赖 mirai-console

主要是由于日志系统和现有生态割裂（不能使用现有的 API 库，破坏了门面模式），且提供的 API 过于麻烦，以前的版本一直通过 hook 等方式续命，现在实在忍不了。

而且 mirai-console 提供的其他 API 也没有明显的优势，甚至会让事情更加复杂。

配置系统重构

mirai-console 的配置系统徒增了复杂度，将参考 Sorapointa 实现重构（也可能是 100% 复制粘贴）。

命令系统重构

mirai-console 的命令系统分词太过抽象，因此将会自行编写基于 clikt 的命令系统。

不变的部分

数据库应该不会变动。

Task 系统应该也不会变动。

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f8a06dbfb82, pid=2255132, tid=2256640
#
# JRE version: OpenJDK Runtime Environment (17.0.7+7) (build 17.0.7+7-Debian-1deb11u1)
# Java VM: OpenJDK 64-Bit Server VM (17.0.7+7-Debian-1deb11u1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0xbe0b82]  ObjectMonitor::exit(JavaThread*, bool)+0x22
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /root/a/bikkuri/hs_err_pid2255132.log
#
# If you would like to submit a bug report, please visit:
#   https://bugs.debian.org/openjdk-17

同时程序中止，重启程序后正常运行

由于上游停止维护（Mirai 以及 QSign），本项目亦将停止维护。

请考虑迁移至手动方案。