[root@VM-0-3-centos mcl]# ./mcl
15:39:20 [INFO] iTX Technologies Mirai Console Loader version 2.1.2-61c8bd8
15:39:20 [INFO] Runtime: OpenJDK 64-Bit Server VM 17.0.6 (arch: 64)
15:39:20 [INFO] https://github.com/iTXTech/mirai-console-loader
15:39:20 [INFO] This program is licensed under GNU AGPL v3
15:39:21 [INFO] Mirai Console Loader Announcement:
Mirai Console Loader 公告栏

如果在图片上传的时候遇到问题请与我们联系 (需要提供图片文件源本)
- 如 Unsupported image type for ExternalResource * considering use gif/png/bmp/jpg format.
`- Tracker: https://github.com/mamoe/mirai/issues/new/choose

常用资源整合
`- https://mirai.mamoe.net/topic/653

MCL 已推出 2.1.0，更好的支持 Mirai 2.11 的插件系统，建议更新。

15:39:21 [INFO] Verifying "net.mamoe:mirai-console" v2.16.0-RC
15:39:21 [INFO] Verifying "net.mamoe:mirai-console-terminal" v2.16.0-RC
15:39:22 [INFO] Verifying "net.mamoe:mirai-core-all" v2.16.0-RC
15:39:22 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1
15:39:22 [INFO] Verifying "net.mamoe:chat-command" v0.5.1
15:39:22 [INFO] Verifying "net.mamoe:mirai-api-http" v2.9.1
15:39:22 [WARN] Package "net.mamoe:chat-command" requires "net.mamoe:mirai-console" version 2.0-RC. Current version is 2.16.0-RC
2023-09-04 15:39:23 I/main: Starting mirai-console...
2023-09-04 15:39:23 I/main:

=================================[ Mirai console 2.16.0-RC ]==================================

| \ / \ \ | / \ |
| ▓▓\ / ▓▓\▓▓ ______ ______ \▓▓ ▓▓▓▓▓▓\ ______ _______ _______ ______ | ▓▓ ______
| ▓▓▓\ / ▓▓▓ / \ | | \ ▓▓ \▓▓/ | \ / / | ▓▓/
| ▓▓▓▓\ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓\ \▓▓▓▓▓▓\ ▓▓ ▓▓ | ▓▓▓▓▓▓\ ▓▓▓▓▓▓▓\ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓\ ▓▓ ▓▓▓▓▓▓
| ▓▓\▓▓ ▓▓ ▓▓ ▓▓ ▓▓ \▓▓/ ▓▓ ▓▓ ▓▓ | ▓▓ | ▓▓ ▓▓ | ▓▓\▓▓ | ▓▓ | ▓▓ ▓▓ ▓▓ ▓▓
| ▓▓ \▓▓▓| ▓▓ ▓▓ ▓▓ | ▓▓▓▓▓▓▓ ▓▓ ▓▓/ \ ▓▓__/ ▓▓ ▓▓ | ▓▓_\▓▓▓▓▓▓\ ▓▓__/ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓
| ▓▓ \▓ | ▓▓ ▓▓ ▓▓ \▓▓ ▓▓ ▓▓\▓▓ ▓▓\▓▓ ▓▓ ▓▓ | ▓▓ ▓▓\▓▓ ▓▓ ▓▓\▓▓
\▓▓ \▓▓\▓▓\▓▓ \▓▓▓▓▓▓▓\▓▓ \▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓\▓▓▓▓▓▓▓ \▓▓▓▓▓▓ \▓▓ \▓▓▓▓▓▓▓

2023-09-04 15:39:23 I/main: Backend: version 2.16.0-RC, built on 2023-09-03 23:55:17.
2023-09-04 15:39:23 I/main: Frontend Terminal: version 2.16.0-RC, provided by Mamoe Technologies
2023-09-04 15:39:23 I/main: Welcome to visit https://mirai.mamoe.net/
2023-09-04 15:39:24 I/plugin: Successfully loaded plugin Chat Command v0.5.0
2023-09-04 15:39:24 I/plugin: Successfully loaded plugin tiktok-link-resolver v0.1.0
2023-09-04 15:39:24 I/QRLogin: Loading QRLogin v0.2.0
2023-09-04 15:39:24 W/QRLogin: 本插件仅在 2.15.0 或以上工作，且在正式版或先行发布版(RC)中可能无法使用
2023-09-04 15:39:24 I/plugin: Successfully loaded plugin QRLogin v0.2.0
2023-09-04 15:39:24 I/fix-protocol-version: 协议版本检查更新...
2023-09-04 15:39:24 I/fix-protocol-version: ANDROID_PHONE load from file:///root/content/apps/back/mcl/android_phone.json
2023-09-04 15:39:25 I/fix-protocol-version: ANDROID_PAD load from file:///root/content/apps/back/mcl/android_pad.json
2023-09-04 15:39:25 I/fix-protocol-version: 注册服务...
2023-09-04 15:39:25 I/fix-protocol-version: 服务配置文件:
file:///root/content/apps/back/mcl/KFCFactory.json
2023-09-04 15:39:25 I/plugin: Successfully loaded plugin fix-protocol-version v1.9.11
2023-09-04 15:39:25 I/plugin: Cannot load plugin mirai-api-http v2.9.1
2023-09-04 15:39:25 E/main: Failed to init MiraiConsole.
net.mamoe.mirai.console.plugin.loader.PluginLoadException: Exception while loading mirai-api-http v2.9.1
at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:373)
at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:40)
at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt)
at net.mamoe.mirai.console.plugin.jvm.JvmPluginLoader$BuiltIn.load(JvmPluginLoader.kt:54)
at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadPluginNoEnable(PluginManagerImpl.kt:100)
at net.mamoe.mirai.console.internal.plugin.PluginManagerImpl.loadAllPluginsUsingBuiltInLoaders$mirai_console(PluginManagerImpl.kt:164)
at net.mamoe.mirai.console.internal.MiraiConsoleImplementationBridge.doStart$mirai_console(MiraiConsoleImplementationBridge.kt:303)
at net.mamoe.mirai.console.MiraiConsoleImplementation$Companion.start(MiraiConsoleImplementation.kt:512)
at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon(MiraiConsoleTerminalLoader.kt:182)
at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.startAsDaemon$default(MiraiConsoleTerminalLoader.kt:181)
at net.mamoe.mirai.console.terminal.MiraiConsoleTerminalLoader.main(MiraiConsoleTerminalLoader.kt:59)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.itxtech.mcl.Utility.bootJars(Utility.java:86)
at org.itxtech.mcl.Utility.bootJars(Utility.java:76)
at org.itxtech.mcl.Utility.bootMirai(Utility.java:98)
at org.itxtech.mcl.module.builtin.Boot.boot(Boot.java:113)
at org.itxtech.mcl.module.ModuleManager.phaseBoot(ModuleManager.java:123)
at org.itxtech.mcl.Loader.lambda$start$4(Loader.java:196)
at org.itxtech.mcl.Loader.tryCatching(Loader.java:151)
at org.itxtech.mcl.Loader.start(Loader.java:196)
at org.itxtech.mcl.Loader.main(Loader.java:84)
Caused by: java.lang.IllegalStateException: A JvmPlugin loaded by plugin.yml must has same description reference
at net.mamoe.mirai.console.internal.plugin.BuiltInJvmPluginLoaderImpl.load(BuiltInJvmPluginLoaderImpl.kt:362)
... 23 more

[root@VM-0-3-centos mcl]#

通过mirai-api-http借助python开发时，使用多个已有python库均无法使用，查询原因是v1-v2的迁移问题，我先是对网上已有的库进行修改后无果，于是我直接使用requests访问，按照迁移文档中的verify流程，得到的依然是404
mcl和mah版本均为最新
c1f68963-c2d4-4481-8c62-3cd5b4baebf5-image.png
aeed46d6-dafd-49ae-a555-d573e5d34abe-image.png

mirai.png

不管用哪个协议登录都报这个,手打也是一样的

2023-08-04 16:32:45 I/MCL Addon: iTXTech MCL Version: 2.1.2-61c8bd8
2023-08-04 16:32:45 W/MCL Addon: iTXTech Soyuz 未安装，Soyuz MCL Handler 特性已禁用
2023-08-04 16:32:45 I/main: 4 plugin(s) enabled.
2023-08-04 16:32:46 I/main: Auto-login 3180675853, protocol: IPAD, heartbeatStrategy: STAT_HB
2023-08-04 16:32:46 W/EncryptService.alert: Encrypt service was loaded: KFCFactory(config=file:///D:/mcl-2.1.2/KFCFactory.json)
2023-08-04 16:32:46 W/EncryptService.alert: All outgoing message may be leaked by this service.
2023-08-04 16:32:46 W/EncryptService.alert: Use this service if and only if you trusted this service and the service provider.
2023-08-04 16:32:46 W/EncryptService.alert: Service details:
2023-08-04 16:32:46 W/EncryptService.alert: - Jvm Class: class xyz.cssxsh.mirai.tool.KFCFactory 2023-08-04 16:32:46 W/EncryptService.alert: - ClassLoader: JvmPluginClassLoader{fix-protocol-version-1.9.10.mirai2.jar}
2023-08-04 16:32:46 W/EncryptService.alert: - Source: file:/D:/mcl-2.1.2/plugins/fix-protocol-version-1.9.10.mirai2.jar 2023-08-04 16:32:46 W/EncryptService.alert: - Protected Domain: ProtectionDomain (file:/D:/mcl-2.1.2/plugins/fix-protocol-version-1.9.10.mirai2.jar <no signer certificates>)
JvmPluginClassLoader{fix-protocol-version-1.9.10.mirai2.jar}
<no principals>
java.security.Permissions@6e67a8c0 (
("java.io.FilePermission" "D:\mcl-2.1.2\plugins\fix-protocol-version-1.9.10.mirai2.jar" "read")
)

2023-08-04 16:32:46 E/KFCFactory: IPAD 尚不支持签名服务，大概率登录失败
2023-08-04 16:32:49 I/TLV544Provider: t544 command: 810_9 with IPAD
2023-08-04 16:32:49 I/Bot.3180675853: Bot cancelled: Bot closed
2023-08-04 16:32:49 E/main: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below.
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263)
at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
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)
Suppressed: java.lang.UnsatisfiedLinkError: xyz.cssxsh.mirai.tool.TLV544Provider.sign$fix_protocol_version([B)[B
at fix-protocol-version-1.9.10.mirai2.jar//xyz.cssxsh.mirai.tool.TLV544Provider.sign$fix_protocol_version(Native Method)
at fix-protocol-version-1.9.10.mirai2.jar//xyz.cssxsh.mirai.tool.TLV544Provider$Companion.sign$fix_protocol_version(TLV544Provider.kt)
at fix-protocol-version-1.9.10.mirai2.jar//xyz.cssxsh.mirai.tool.TLV544Provider.encryptTlv(TLV544Provider.kt:114)
at net.mamoe.mirai.internal.network.protocol.packet.TlvKt.t544ForToken(Tlv.kt:986)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1$1$1$1.invoke(WtLogin9.kt:138)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1$1$1$1.invoke(WtLogin9.kt:39)
at net.mamoe.mirai.utils.TlvMapKt._writeTlvMap(TlvMap.kt:130)
at net.mamoe.mirai.utils.TlvMapKt._writeTlvMap$default(TlvMap.kt:123)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1$1$1.invoke(WtLogin9.kt:39)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1$1$1.invoke(WtLogin9.kt:31)
at net.mamoe.mirai.internal.network.protocol.packet.EncryptMethodEcdh.makeBody(EncryptMethod.kt:121)
at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeOicqRequestPacket(OutgoingPacket.kt:455)
at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeOicqRequestPacket$default(OutgoingPacket.kt:448)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1$1.invoke(WtLogin9.kt:31)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1$1.invoke(WtLogin9.kt:30)
at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeSsoPacket(OutgoingPacket.kt:985)
at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.writeSsoPacket$default(OutgoingPacket.kt:352)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1.invoke(WtLogin9.kt:30)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9$Password$1.invoke(WtLogin9.kt:27)
at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.buildLoginOutgoingPacket(OutgoingPacket.kt:310)
at net.mamoe.mirai.internal.network.protocol.packet.OutgoingPacketKt.buildLoginOutgoingPacket$default(OutgoingPacket.kt:278)
at net.mamoe.mirai.internal.network.protocol.packet.login.wtlogin.WtLogin9.Password(WtLogin9.kt:27)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin$lambda$8$SSOWtLogin9(SsoProcessor.kt:417)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:423)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.doSlowLogin$suspendImpl(SsoProcessor.kt:175)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.doSlowLogin(SsoProcessor.kt)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:273)
at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$login$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 net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.resumeRootWith(SuspendFunctionGun.kt:138)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.loop(SuspendFunctionGun.kt:112)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun.access$loop(SuspendFunctionGun.kt:14)
at net.mamoe.mirai.internal.deps.io.ktor.util.pipeline.SuspendFunctionGun$continuation$1.resumeWith(SuspendFunctionGun.kt:62)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
... 5 more
[CIRCULAR REFERENCE:java.lang.UnsatisfiedLinkError: xyz.cssxsh.mirai.tool.TLV544Provider.sign$fix_protocol_version([B)[B]

2023-08-04 16:32:49 V/Bot.3180675853: Event: net.mamoe.mirai.console.events.AutoLoginEvent$Failure@1939a394
2023-08-04 16:32:49 I/main: mirai-console started successfully.

问题1

对于任意好友消息，引用文本消息的targetId都为0
图1
图2
但是对于ForwardMessage，targetId就是正确的，如问题2的第一张图

问题2

对于任意好友消息，无论对方消息还是自己的消息，无论转发消息还是文本消息，均出现ids对不上号的问题
图1
图2

问题3

对于任意监听到的好友消息，MessageChain的source中的Target都是不正确的
图1
正确的应该如下图这样
图2

还有个概率存在的问题，机器人发送的消息中

log.trace("MessagePostSendEvent..."); OnlineMessageSource.Outgoing source = Objects.requireNonNull(event.getReceipt()).getSource(); source.getIds() // source.getIds() 有时候会返回一个空的int[]数组

从code=45解决到code=237，然后又出现这个问题
d09e97a2-106a-4583-b03d-d766d998815f-image.png

报错截图
屏幕截图 2023-07-23 094912.png屏幕截图 2023-07-23 094931.png

./mcl-installer-ae9f946-linux-amd64: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by ./mcl-installer-ae9f946-linux-amd64)

启动时出现问题

Debian虚拟机未知原因报错

2023-07-04 16:40:20 I/main: Backend: version 2.14.0, built on 2023-02-06 14:25:21. 2023-07-04 16:40:20 I/main: Frontend Terminal: version 2.14.0, provided by Mamoe Technologies 2023-07-04 16:40:20 I/main: Welcome to visit https://mirai.mamoe.net/ java.nio.file.AccessDeniedException: /home/xxxxx/logs/2023-07-04.log at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source) at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(Unknown Source) at java.base/java.nio.file.spi.FileSystemProvider.newOutputStream(Unknown Source) at java.base/java.nio.file.Files.newOutputStream(Unknown Source) at java.base/java.nio.file.Files.newBufferedWriter(Unknown Source) at net.mamoe.mirai.console.frontendbase.logging.DailySplitLogRecorder.acquireFileWriter(LogRecorder.kt:137) at net.mamoe.mirai.console.frontendbase.logging.DailySplitLogRecorder.record(LogRecorder.kt:145) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorderForwarded.asyncRecord(LogRecorder.kt:85) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorder$2.invokeSuspend(LogRecorder.kt:61) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) java.lang.IllegalStateException: Writer not setup at net.mamoe.mirai.console.frontendbase.logging.DailySplitLogRecorder.record(LogRecorder.kt:147) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorderForwarded.asyncRecord(LogRecorder.kt:85) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorder$2.invokeSuspend(LogRecorder.kt:61) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) java.lang.IllegalStateException: Writer not setup at net.mamoe.mirai.console.frontendbase.logging.DailySplitLogRecorder.record(LogRecorder.kt:147) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorderForwarded.asyncRecord(LogRecorder.kt:85) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorder$2.invokeSuspend(LogRecorder.kt:61) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) java.lang.IllegalStateException: Writer not setup at net.mamoe.mirai.console.frontendbase.logging.DailySplitLogRecorder.record(LogRecorder.kt:147) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorderForwarded.asyncRecord(LogRecorder.kt:85) at net.mamoe.mirai.console.frontendbase.logging.AsyncLogRecorder$2.invokeSuspend(LogRecorder.kt:61) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)

目前确实发现了这样一个问题:
描述一下:

我在在测试时使用的是二维码登录 手表协议
在Bot登录成功后, 使用Bot给其他人发消息(仅私聊时), 会触发消息事件. 而且事件中的 sender 不是 Bot自身 而是目标好友

问题版本: 2.15.0-M1, 2.15.0-RC

example:
c9cdf71f-f431-41e3-af7d-a8325a509167-image.png

登录的账号:

be5bf1f7-5da8-4bdc-89c5-11a94c6ee76c-image.png

日志中打印的账号:

ffe06b1a-3691-4974-90ea-ed2208d24bc2-image.png

请问这种情况是正常的吗?

eb447d6c-0bf8-4514-b113-70fa2e263ffe-image.png
已在Maven手动引入版本修复依赖，使用Aoki手动生成device json文件。登陆后还是提示45

屏幕截图 2023-06-22 201852.png
屏幕截图 2023-06-22 202212.png 今天下午还可以登录，在QQ上测试了插件关了之后晚上回来登录后给了冻结，解冻后只能手机登录，mirai上不去哩

7d798606-ac3a-463e-884b-a6a2b9a61fc4-QQ20230623-001851.png QQ20230623-001851.png

Mirai登录后报错
2023-05-20 19:34:30 E/main: Exception in coroutine Bot 3127201349.MessageSvcSyncerImpl
java.lang.IllegalStateException: NetworkHandler is already closed.
at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateClosed.sendPacketImpl(CommonNetworkHandler.kt:389)
at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler.sendPacketImpl(CommonNetworkHandler.kt:36)
at net.mamoe.mirai.internal.network.handler.NetworkHandlerSupport.sendAndExpect(NetworkHandlerSupport.kt:123)
at net.mamoe.mirai.internal.network.handler.NetworkHandlerSupport$sendAndExpect$1.invokeSuspend(NetworkHandlerSupport.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:104)
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)
Suppressed: kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms
at kotlinx.coroutines.TimeoutKt.TimeoutCancellationException(Timeout.kt:184)
at kotlinx.coroutines.TimeoutCoroutine.run(Timeout.kt:154)
at kotlinx.coroutines.EventLoopImplBase$DelayedRunnableTask.run(EventLoop.common.kt:508)
at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:284)
at kotlinx.coroutines.DefaultExecutor.run(DefaultExecutor.kt:108)
at java.base/java.lang.Thread.run(Unknown Source)

运行环境：
Java 17 OpenJ9
Mirai 2.14

注册bot bean的代码

@Bean public Bot bot(){ //创建bot配置类 BotConfiguration botConfiguration = new BotConfiguration(); //设置配置 botConfiguration.setCacheDir(new File(BOT_PATH)); //BOT_PATH 为定义好的常量 botConfiguration.setHeartbeatStrategy(BotConfiguration.HeartbeatStrategy.REGISTER); botConfiguration.setProtocol(BotConfiguration.MiraiProtocol.IPAD); botConfiguration.setWorkingDir(new File(BOT_PATH)); File logdir = new File(BOT_PATH+"log"); if (!logdir.isDirectory()) logdir.mkdirs(); botConfiguration.redirectBotLogToDirectory(logdir); botConfiguration.redirectNetworkLogToDirectory(logdir); botConfiguration.fileBasedDeviceInfo(); botConfiguration.enableContactCache(); botConfiguration.getContactListCache().setSaveIntervalMillis(60000*30); //配置完成，注册bot Bot bot = BotFactory.INSTANCE.newBot(QQ,PASSWORD,botConfiguration); //QQ,PASSWORD也是定义好的常量 //注册监听 messageListener需要继承SimpleListenerHost类 bot.getEventChannel().parentScope(messageListener).registerListenerHost(messageListener); return bot; }

在2.12.3包括之前的任意版本都可以正常工作,但是更新至2.13.x之后的任何版本,都会出现

Caused by: java.util.ServiceConfigurationError: net.mamoe.mirai.IMirai: Provider net.mamoe.mirai.internal.MiraiImpl could not be instantiated at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:586) ~[na:na] at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:813) ~[na:na] at java.base/java.util.ServiceLoader$ProviderImpl.get(ServiceLoader.java:729) ~[na:na] at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1403) ~[na:na] at kotlin.collections.CollectionsKt___CollectionsKt.firstOrNull(_Collections.kt:270) ~[kotlin-stdlib-1.5.10.jar:1.5.10-release-890 (1.5.10)] at net.mamoe.mirai.utils.ServicesKt.loadService(Services.kt:18) ~[mirai-core-utils-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.Mirai.findMiraiInstance(IMirai.kt:357) ~[mirai-core-api-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai._MiraiInstance.get(IMirai.kt:348) ~[mirai-core-api-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.Mirai.getInstance(IMirai.kt:39) ~[mirai-core-api-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.internal.message.MessageSerializersImpl.getSerializersModule(MessageSerializersImpl.kt:65) ~[mirai-core-api-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.internal.message.MessageSerializersImpl.registerSerializers(MessageSerializersImpl.kt:76) ~[mirai-core-api-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.message.MessageSerializers$INSTANCE.registerSerializers(MessageSerializers.kt) ~[mirai-core-api-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.internal.message.protocol.MessageProtocolFacade.<clinit>(MessageProtocolFacade.kt:165) ~[mirai-core-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.internal.MiraiImplKt._MiraiImpl_static_init(MiraiImpl.kt:25) ~[mirai-core-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.internal.MiraiImpl.<clinit>(MiraiImpl.kt:87) ~[mirai-core-jvm-2.13.0.jar:2.13.0] at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:na] at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77) ~[na:na] at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:na] at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) ~[na:na] at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) ~[na:na] at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:789) ~[na:na] ... 53 common frames omitted Caused by: java.lang.NoClassDefFoundError: net/mamoe/mirai/internal/deps/io/ktor/client/engine/okhttp/OkHttp at net.mamoe.mirai.internal.MiraiImplKt.createDefaultHttpClient(MiraiImpl.kt:29) ~[mirai-core-jvm-2.13.0.jar:2.13.0] at net.mamoe.mirai.internal.MiraiImpl.<init>(MiraiImpl.kt:97) ~[mirai-core-jvm-2.13.0.jar:2.13.0] at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:na] at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77) ~[na:na] at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:na] at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) ~[na:na] at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) ~[na:na] at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:789) ~[na:na] ... 72 common frames omitted Caused by: java.lang.ClassNotFoundException: net.mamoe.mirai.internal.deps.io.ktor.client.engine.okhttp.OkHttp at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) ~[na:na] at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) ~[na:na] at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520) ~[na:na] ... 80 common frames omitted 进程已结束,退出代码1

我添加了 okhttp 的依赖项也无法解决 pom文件:

<properties> <mirai.version>2.13.0</mirai.version> </properties> <dependency> <groupId>net.mamoe</groupId> <artifactId>mirai-core-jvm</artifactId> <version>${mirai.version}</version> </dependency> <dependency> <groupId>com.squareup.okhttp3</groupId> <artifactId>okhttp</artifactId> <version>4.8.1</version> <scope>compile</scope> </dependency>

我不知道如何解决 Okhttp 的依赖冲突(如果问题是这个的话,因为看包名net/mamoe/mirai/internal/deps/io/ktor/client/engine/okhttp/OkHttp似乎是在mirai自己内部实现了,不应该外部管理?)

没有风控，大部分指令发出去之后隔半天才有反应，要不就无反应。插件的消息控制台能看到发出去了实际上群里or单聊都接收不到，请问是咋回事

BotFactory.INSTANCE.newBot(2770098376, "11", botConfiguration);
报错，显示整数过大
maven版本信息

<dependency> <groupId>net.mamoe</groupId> <artifactId>mirai-core-jvm</artifactId> <version>2.9.2</version> </dependency>

试过了很多方法，登陆不上的文章已经看了 ，还有什么方法解决吗？

今天下午开始突然群聊不能发送转发的消息，不能发送正常消息，图片，但是可以分享网易云。好友一切正常 2.15mirai ANDROID_WATCH
2023-05-30 15:51:32 V/Bot.3620136843: [<$ǿĀD>布<$ÿĀ>响<$ÿĀ>丸<$ÿĀ>辣<$ǿĀD>(786634372)] 魔理沙的八卦炉(1244544779) -> 抽老婆
2023-05-30 15:51:35 V/Bot.3620136843: Group(786634372) <- [mirai:at:1244544779] 今天你的群友亲爱的是 [mirai:image:{F30A4FB2-EB91-47F0-F2AF-C25E0C745D78}.jpg, width=640, height=640, size=29877, type=UNKNOWN, isEmoji=false]
【鱼塘】(2731851326)哒！
2023-05-30 15:51:37 V/Bot.3620136843: [<$ǿĀD>布<$ÿĀ>响<$ÿĀ>丸<$ÿĀ>辣<$ǿĀD>(786634372)] 魔理沙的八卦炉(1244544779) -> #网易 大貔貅
2023-05-30 15:51:38 V/Bot.3620136843: Group(786634372) <- MusicShare(kind=NeteaseCloudMusic, title=大貔貅, summary=ONER, jumpUrl=https://y.music.163.com/m/song?id=2014304695, pictureUrl=http://p4.music.126.net/2okZp9SEpBMq74Dgahtapw==/109951168232352753.jpg, musicUrl=http://music.163.com/song/media/outer/url?id=2014304695.mp3, brief=[分享]大貔貅)

这段程序在服务器上跑了一个多月了，一直正常，但是这周突然频发有机器人不回复消息的情况，我刚开始以为是我的程序报错了，一查日志发现我的程序没问题，通过http发送群消息的时候，msg是SUCCESS，CODE也是0，但是消息就是没有回复到群里，messageId也是-1
请问这是什么原因？
替代文字
环境信息：
mirai ：Version 2.15.0-M1
mirai-api-http：Version 2.9.1
登录方式：qrlogin 手表