Skip to content

fix: 游戏关闭后无法结束自身进程 - #363

Merged
MistEO merged 1 commit into
MistEO:mainfrom
zmdyy0318:fix/self-stop-after-game-closed
Sep 29, 2026
Merged

MistEO merged 1 commit into
MistEO:mainfrom
zmdyy0318:fix/self-stop-after-game-closed

Conversation

@zmdyy0318

@zmdyy0318 zmdyy0318 commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor
image 因游戏被杀了以后,request_tasker_stop会返回失败,导致无法关闭mxu

关闭mxu属于最后一个任务,暂时忽略返回值让结束自身继续跑

close MaaEnd/MaaEnd#5930

Made with Cursor

Sourcery 摘要

错误修复:

  • 当控制器已断开连接导致任务执行器停止请求发布失败时,允许优雅的自停止流程继续执行,确保前端仍能收到自停止通知并退出。
Original summary in English

Summary by Sourcery

Bug Fixes:

  • Allow graceful self-stop to continue when posting the tasker stop request fails because the controller has already disconnected, ensuring the frontend still receives the self-stop notification and exits.

关闭游戏后 Win32 控制器已断开,MaaTaskerPostStop 投递停止任务会失败。结束自身时不再把这次失败当成硬错误,继续通知前端退出。

Co-authored-by: Cursor <cursoragent@cursor.com>

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

嗨——我已经审阅了你的更改,看起来很棒!


Sourcery 对开源项目免费——如果你喜欢我们的审阅,请考虑分享它们 ✨
Original comment in English

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@MistEO
MistEO merged commit 9fa8cc5 into MistEO:main Sep 29, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

【结束进程】结束自身进程功能 未能成功执行

2 participants