Manyana，free dalle3、asmr推送、动漫角色识别、gal查询、对话模型+语音、黑神话wiki、漂流瓶等功能集合，一键部署
-
-
@Anstiya 文本转语音可以开发一个这样的功能吗：将自定义回复匹配的文本转化为指定音源的语音，然后自动输出
-
This post is deleted! -
Referenced by
Anstiya
-
@bujidao 更了
-
This post is deleted! -
把Pandora_chatGPT加进了项目中，继续白嫖gpt3.5
-
Referenced by
-
chatglm能不能用
-
希望能加个SD的绘画调用以及本地部署的chatglm调用
-
@shenleqinai SD的话，这里，C佬这个插件已经很健全了。
chatGLM之后我看看吧，目前用rwkv是因为b站有人发过rwkv一键部署教程，更方便一些，如果感兴趣也可以考虑下。 -
@shenleqinai 下午做了智谱ai的chatGLMapi调用，还是比较有性价比的，可以考虑，整体效果也不错。😋
-
麻烦问一下，机器人进群后不说话是什么情况呀，后台看也能接收到对话。安装的音乐插件倒是正常运行和正常回复，其他的比如@后 帮助，就不回复
-
@w211691 main.py启动了吗，启动了的话会出彩色字体
-
Referenced by
-
2023-10-26 14:08:53 I/UnidbgFetchQsign: Bot(*) destroy, Instance destroyed successfully.
Login failed: unidbg-fetch-qsign 服务异常, 请检查其日志, 'java.util.ConcurrentModificationException'
2023-10-26 14:08:53 E/console: xyz.cssxsh.mirai.tool.KFCStateException: unidbg-fetch-qsign 服务异常, 请检查其日志, 'java.util.ConcurrentModificationException'
xyz.cssxsh.mirai.tool.KFCStateException: unidbg-fetch-qsign 服务异常, 请检查其日志, 'java.util.ConcurrentModificationException'
at fix-protocol-version-1.12.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.check(UnidbgFetchQsign.kt:109)
at fix-protocol-version-1.12.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.customEnergy(UnidbgFetchQsign.kt:137)
at fix-protocol-version-1.12.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.encryptTlv(UnidbgFetchQsign.kt:125)
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.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)2023-10-26 14:08:53 I/Bot.*: Bot cancelled: Bot closed
Traceback (most recent call last):
File "main.py", line 217, in <module>
File "main.py", line 163, in runBot
File "subprocess.py", line 947, in init
File "subprocess.py", line 1416, in _execute_child
NotADirectoryError: [WinError 267] 目录名称无效。
[16156] Failed to execute script 'main' due to unhandled exception! -
@DXloader 2023-10-26 14:08:53 I/Bot.*: Bot cancelled: Bot closed之前的部分是qsign配置或者登陆的问题，bot没有成功登录。你可以尝试release的ManyanaLauncher.rar，其中放置了从80到85的qisn版本，可自行切换(默认80)。
对于NotADirectoryError: [WinError 267] 目录名称无效。
[16156] Failed to execute script 'main' due to unhandled exception!
你需要确保完整克隆了Manyana仓库，即Manyana文件夹中的内容完整，为便于通过git更新，上面说的ManyanaLauncher.rar中并不包含Manyana源码，你可以手动执行Launcher的搭建流程以获取源码，或在任意目录打开cmd执行
git clone https://github.com/avilliai/Manyana.git不建议通过Launcher启动bot
用Launcher启动与你手动依次启动下面三个文件是一样的
qsign/sever.cmd
miraibot/内存溢出用这个启动.cmd
Manyana/启动脚本.bat
前两个，即qsign和miraibot和你自己搭的qsign和mcl(已安装mirai-api-http 并正确配置)并无区别 -
This post is deleted! -
- 接入arona-api
- 更新了搭建工具。
-
- Serving Flask app 'flask_voice'
- Debug mode: on
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. - Running on http://127.0.0.1:9081
Press CTRL+C to quit - Restarting with stat
- Debugger is active!
- Debugger PIN: 280-617-066
2023-12-05 03:47:07 - ERROR
Traceback (most recent call last):
File "D:\Manyana\venv\lib\site-packages\mirai\utils.py", line 20, in async_with_exception
return await async_(obj)
File "D:\Manyana\venv\lib\site-packages\mirai\utils.py", line 14, in async_
return (await obj) if inspect.isawaitable(obj) else obj
File "D:\Manyana\venv\lib\site-packages\mirai\models\bus.py", line 63, in middleware
return await async_with_exception(func(event_model))
File "D:\Manyana\run\musicShare.py", line 176, in stop_scheduler
scheduler.shutdown(True) # 结束定时器
File "D:\Manyana\venv\lib\site-packages\apscheduler\schedulers\asyncio.py", line 13, in wrapper
self._eventloop.call_soon_threadsafe(wrapped)
AttributeError: 'NoneType' object has no attribute 'call_soon_threadsafe'
Traceback (most recent call last):
File "D:\Manyana\venv\lib\site-packages\websockets\legacy\client.py", line 666, in await_impl
await protocol.handshake(
File "D:\Manyana\venv\lib\site-packages\websockets\legacy\client.py", line 332, in handshake
raise InvalidStatusCode(status_code, response_headers)
websockets.exceptions.InvalidStatusCode: server rejected WebSocket connection: HTTP 404
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\Manyana\venv\lib\site-packages\websockets\legacy\client.py", line 680, in await_impl
await protocol.wait_closed()
asyncio.exceptions.CancelledErrorDuring handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:\users\admin\appdata\local\programs\python\python39\lib\asyncio\tasks.py", line 487, in wait_for
fut.result()
asyncio.exceptions.CancelledErrorThe above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "D:\Manyana\main.py", line 218, in <module>
bot.run()
File "D:\Manyana\venv\lib\site-packages\mirai\bot.py", line 199, in run
MiraiRunner(self).run(host, port, asgi_server, **kwargs)
File "D:\Manyana\venv\lib\site-packages\mirai\bot.py", line 276, in run
asyncio.run(self._run())
File "c:\users\admin\appdata\local\programs\python\python39\lib\asyncio\runners.py", line 44, in run
return loop.run_until_complete(main)
File "c:\users\admin\appdata\local\programs\python\python39\lib\asyncio\base_events.py", line 642, in run_until_complete
return future.result()
File "D:\Manyana\venv\lib\site-packages\mirai\bot.py", line 240, in _run
await self.startup()
File "D:\Manyana\venv\lib\site-packages\mirai\bot.py", line 228, in startup
await asyncio.gather(*coros)
File "D:\Manyana\venv\lib\site-packages\mirai\bot.py", line 137, in startup
await self._adapter.login(self.qq)
File "D:\Manyana\venv\lib\site-packages\mirai\adapters\base.py", line 35, in wrapped
return await func(self, *args, **kwargs)
File "D:\Manyana\venv\lib\site-packages\mirai\adapters\websocket.py", line 187, in login
self.connection = await connect(self.host_name, extra_headers=headers)
File "D:\Manyana\venv\lib\site-packages\websockets\legacy\client.py", line 659, in await_impl_timeout
return await asyncio.wait_for(self.await_impl(), self.open_timeout)
File "c:\users\admin\appdata\local\programs\python\python39\lib\asyncio\tasks.py", line 489, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError -
@konearca mcl那边确保已经登陆账号
如果你用的release整合包
{"botName": "机器人名字", "botQQ": "机器人QQ", "master": "你的QQ","mainGroup": "你的群", "vertify_key": "1234567890", "port": "23456"}确保机器人QQ务必对应，后两项无需修改
自己搭的mirai
确保已安装mirai-api-http 并正确配置
如果自行安装了uvicorn或hypercorn
pip uninstall uvicorn
pip uninstall hypercorn -
插件在启动后过几分钟后就像卡死了一样，bot那边能接收到消息但是插件没有反应，后台占用也是几乎没有，请问这是什么情况
-
@konearca 截个图看看。
启动时有没有收到bot给你发送启动成功的私信。
