Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

调试环境和实际运行时不一致

Aperta
#76 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

Inizia con script_runner.py alle righe indicate 158, 192, 658 e 672, quindi riproduci sia il fallimento interno dell’esecuzione Python sia l’arresto non riuscito di Endfield.exe a partire dai log forniti. Confronta il comportamento di debug con quello effettivo a runtime e traccia i percorsi di ritentativo e di pulizia dei processi. Il lavoro è completato quando i fallimenti di runtime e di terminazione dei processi segnalati sono riproducibili, spiegati e coperti da un comportamento verificato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

1,我留意到 https://github.com/OneDragon-Anything/OneDragon-ScriptChainer/issues/52
我调试的时候没报错,实际运行还是出问题,看起来调试环境和实际运行时不一致的问题还没解决?

[04:00:19.159] [script_runner.py 158] [INFO]: 执行 Python 脚本 米游社签到...
[04:00:19.290] [script_runner.py 158] [INFO]: Python 脚本执行失败 米游社签到: No module named 'uuid'
[04:00:19.290] [script_runner.py 672] [ERROR]: Python 脚本执行失败
Traceback (most recent call last):
File "script_runner.py", line 658, in _run_python_script
File "D:\04.GameTools\00.General\01.sign\MihoyoBBSTools\main.py", line 9, in
import tools
File "D:\04.GameTools\00.General\01.sign\MihoyoBBSTools\tools.py", line 5, in
import uuid
ModuleNotFoundError: No module named 'uuid'

目前我就让 ai 弄了个 bat 指定用我自己装的 python(新增脚本 - 外部程序),不知道你说的“使用内部脚本的subprocess调用那边的虚拟环境解释器运行”是不是也是这个意思?

Image

2

[05:16:55.092] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:16:55.093] 补充理智
[05:17:14.654] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:17:14.639] 行动成功次数已满,结束任务
[05:17:41.511] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:17:41.506] 任务完成: ⚔️协议空间
[05:17:42.062] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:17:42.062] 任务开始: 🎁赠送干员礼物
[05:22:42.488] [script_runner.py 158] [INFO]: 脚本超过 300 秒无日志输出,判定为未响应 MaaEnd.exe
[05:22:42.611] [script_runner.py 158] [INFO]: 尝试关闭脚本进程 MaaEnd.exe (pid=6064)
[05:22:43.433] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.432][ERR][Px6064][Tx1103][ScreenDCScreencap.cpp][L28][MaaNS::CtrlUnitNs::ScreenDCScreencap::screencap] GetWindowRect failed, error code: 1400 
[05:22:43.433] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.432][ERR][Px6064][Tx1103][Win32ControlUnitMgr.cpp][L424][MaaNS::CtrlUnitNs::Win32ControlUnitMgr::screencap] failed to screencap 
[05:22:43.434] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.432][ERR][Px6064][Tx1103][ControllerAgent.cpp][L802][MaaNS::ControllerNS::ControllerAgent::handle_screencap] controller screencap failed 
[05:22:43.434] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.434][ERR][Px6064][Tx11466][ActionHelper.cpp][L122][MaaNS::TaskNS::ActionHelper::wait_freezes] Image is empty [pre_image.empty()=false] [cur_image.empty()=true] 
[05:22:43.439] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.439][ERR][Px6064][Tx1103][ScreenDCScreencap.cpp][L28][MaaNS::CtrlUnitNs::ScreenDCScreencap::screencap] GetWindowRect failed, error code: 1400 
[05:22:43.439] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.439][ERR][Px6064][Tx1103][Win32ControlUnitMgr.cpp][L424][MaaNS::CtrlUnitNs::Win32ControlUnitMgr::screencap] failed to screencap 
[05:22:43.439] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:43.439][ERR][Px6064][Tx1103][ControllerAgent.cpp][L802][MaaNS::ControllerNS::ControllerAgent::handle_screencap] controller screencap failed 
[05:22:44.444] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:44.443][ERR][Px6064][Tx1103][ScreenDCScreencap.cpp][L28][MaaNS::CtrlUnitNs::ScreenDCScreencap::screencap] GetWindowRect failed, error code: 1400 
[05:22:44.444] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:44.443][ERR][Px6064][Tx1103][Win32ControlUnitMgr.cpp][L424][MaaNS::CtrlUnitNs::Win32ControlUnitMgr::screencap] failed to screencap 
[05:22:44.444] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:22:44.443][ERR][Px6064][Tx1103][ControllerAgent.cpp][L802][MaaNS::ControllerNS::ControllerAgent::handle_screencap] controller screencap failed 
[05:22:45.727] [script_runner.py 158] [INFO]: 尝试关闭游戏进程 Endfield.exe
[05:22:45.844] [script_runner.py 158] [INFO]: 重试运行脚本 (1/2) MaaEnd.exe
[05:22:45.977] [script_runner.py 158] [INFO]: 脚本进程启动成功 D:\04.GameTools\06.AKE\MaaEnd\MaaEnd.exe
[05:22:46.096] [script_runner.py 158] [INFO]: 创建脚本子进程 D:\04.GameTools\06.AKE\MaaEnd\MaaEnd.exe
[05:22:46.210] [script_runner.py 158] [INFO]: 脚本子进程创建成功 D:\04.GameTools\06.AKE\MaaEnd\MaaEnd.exe
[05:22:46.326] [script_runner.py 158] [INFO]: 等待打开 终末地
[05:22:46.445] [script_runner.py 158] [INFO]: 如长时间未检测到进程,请检查“游戏进程名称”填写是否正确:Endfield.exe
[05:23:05.852] [script_runner.py 192] [INFO]: [脚本] [0919/052305.851:ERROR:ui\gfx\win\window_impl.cc:172] Failed to unregister class Chrome_WidgetWin_0. Error = 1412
[05:23:06.709] [script_runner.py 158] [INFO]: 游戏或脚本被关闭 终末地
[05:23:06.810] [script_runner.py 158] [INFO]: 尝试关闭脚本进程 None (pid=12360)
[05:23:07.947] [script_runner.py 158] [INFO]: 尝试关闭游戏进程 Endfield.exe
[05:23:08.112] [script_runner.py 158] [INFO]: 10秒后开始下一个脚本
[05:23:12.128] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:23:12.128] 正在执行前置程序: Endfield.exe...
[05:23:12.230] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:23:12.228] 前置程序 Endfield.exe 执行完成
[05:23:12.287] [script_runner.py 192] [INFO]: [脚本] [2026-09-19 05:23:12.287] 正在等待窗口「Endfield」就绪...
[05:23:18.226] [script_runner.py 158] [INFO]: 脚本进程启动成功 D:\04.GameTools\01.GI\BetterGI\BetterGI.exe
[05:23:18.343] [script_runner.py 158] [INFO]: 创建脚本子进程 D:\04.GameTools\01.GI\BetterGI\BetterGI.exe
[05:23:18.445] [script_runner.py 158] [INFO]: 脚本子进程创建成功 D:\04.GameTools\01.GI\BetterGI\BetterGI.exe

日志是这样的,早上看到的时候发现终末地没有成功被关闭还开着,原神也在跑,关闭 endfiled.exe 进程没成功

Lingua principale
Python
Stelle
217
Fork
14
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OneDragon-Anything/OneDragon-ScriptChainer

Tutte le issue di OneDragon-Anything/OneDragon-ScriptChainer

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.