2025-07-19 17:30 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004295Spring engineLuapublic2014-02-03 05:25
Reportermsafwan 
Assigned TojK 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version96.0.1+git 
Target VersionFixed in Version 
Summary0004295: [Internal Lua error] error, unknown general LUA malfunction, can't do /reload
DescriptionAfter Spring 96.0.1-147-ge82a681 (above this version ! have trouble) I got this error when I use a combination of widget:
[f=0000930] Error: LuaUI::RunCallIn: error = 2, CommandNotifyMex, [Internal Lua error: Traceback failure] attempt to call a number value

Combination of widget:
A widget mex_placement.lua (in ZK) call Luaui.script.CommandNotifyMex to notify for mex build order as an EVENT and another widget unit_central_build_ai.lua intercept it and return false/true to change behaviour in mex_placement.lua.

Also, /reload did not work when I try it recently (in latest Spring from Bleeding Edge), seems to imply a general LUAUI unknown failure.
Additional InformationI try to bisect a specific build, but above Spring 96.0.1-147-ge82a681 there's a gap with no Win32 build.
Tagsluaui
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0012772

msafwan (reporter)

F11 button binded to widget-selector widget also doesn't work.

~0012783

abma (administrator)

see 0004293 for F11

~0012804

abma (administrator)

maybe related to 0004301

~0012805

abma (administrator)

96.0.1-147-ge82a681 is the last commit before luasynced_split merge
+Notes

-Issue History
Date Modified Username Field Change
2014-01-28 12:44 msafwan New Issue
2014-01-28 12:45 msafwan Tag Attached: luaui
2014-01-28 12:49 msafwan Note Added: 0012772
2014-01-30 14:22 abma Note Added: 0012783
2014-01-31 19:58 abma Note Added: 0012804
2014-01-31 20:00 abma Note Added: 0012805
2014-02-03 05:25 jK Changeset attached => spring develop 2e69d471
2014-02-03 05:25 jK Assigned To => jK
2014-02-03 05:25 jK Status new => resolved
2014-02-03 05:25 jK Resolution open => fixed
+Issue History