Description
I'm trying to update Aegisub-Motion to v1.1.0 using DependencyControl's Update Script tool in an installed Aegisub on Windows 11.
When I select Aegisub-Motion and start the update, DependencyControl begins updating its dependencies, but eventually enters a recursive update chain involving the Tags module.
The update then fails with a Lua runtime error.
Steps to reproduce
- Open Aegisub.
- Open DependencyControl's Update Script tool.
- Select
Aegisub-Motion.
- Start the update.
- DependencyControl begins updating the required modules.
- The update eventually reaches
Tags again while its previous update task is still running.
Expected behavior
DependencyControl should successfully resolve and update all required dependencies of Aegisub-Motion, or detect the dependency cycle and terminate the update gracefully with a meaningful error message.
Actual behavior
The update reaches the following sequence:
Aegisub-Motion
└─ LineCollection
└─ Line
└─ Tags
└─ Transform
└─ Tags
At this point DependencyControl reports:
Skipped update of module 'Tags': the update task is already running.
However, instead of gracefully handling this situation, it eventually throws a Lua runtime error:
attempt to call field 'getUpdaterErrorMsg' (a nil value)
Full error log
Starting update of automation script 'Aegisub-Motion'...
Checking requirements...
— Updating outdated module 'LineCollection'...
— Starting update of module 'LineCollection'...
— Checking requirements...
—— Updating outdated module 'Line'...
—— Starting update of module 'Line'...
—— Checking requirements...
——— Updating outdated module 'Tags'...
——— Starting update of module 'Tags'...
——— Checking requirements...
———— Updating outdated module 'Transform'...
———— Starting update of module 'Transform'...
———— Checking requirements...
————— Updating outdated module 'Tags'...
————— Starting update of module 'Tags'...
————— Skipped update of module 'Tags': the update task is already running.
Lua reported a runtime error:
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 661
<anonymous function at lines 532-673>
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 911
performUpdate
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\ModuleLoader.moon", line 169
loadModules
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\Updater.moon", line 119
require
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 661
run
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 911
performUpdate
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\ModuleLoader.moon", line 169
loadModules
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\Updater.moon", line 119
require
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 661
run
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 911
performUpdate
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\ModuleLoader.moon", line 169
loadModules
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\Updater.moon", line 119
require
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 661
run
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\UpdateTask.moon", line 911
performUpdate
File "C:\Users\newad\AppData\Roaming\Aegisub\automation\include\l0\DependencyControl\ModuleLoader.moon", line 174
loadModules
attempt to call field 'getUpdaterErrorMsg' (a nil value)
Could someone confirm whether this is a known issue with the current DependencyControl updater, or whether the dependency definitions in Aegisub-Motion v1.1.0 need to be adjusted?
Thanks!
Description
I'm trying to update Aegisub-Motion to v1.1.0 using DependencyControl's Update Script tool in an installed Aegisub on Windows 11.
When I select
Aegisub-Motionand start the update, DependencyControl begins updating its dependencies, but eventually enters a recursive update chain involving theTagsmodule.The update then fails with a Lua runtime error.
Steps to reproduce
Aegisub-Motion.Tagsagain while its previous update task is still running.Expected behavior
DependencyControl should successfully resolve and update all required dependencies of Aegisub-Motion, or detect the dependency cycle and terminate the update gracefully with a meaningful error message.
Actual behavior
The update reaches the following sequence:
At this point DependencyControl reports:
However, instead of gracefully handling this situation, it eventually throws a Lua runtime error:
Full error log
Could someone confirm whether this is a known issue with the current DependencyControl updater, or whether the dependency definitions in Aegisub-Motion v1.1.0 need to be adjusted?
Thanks!