misc/wagon.lua:17: attempt to perform arithmetic on local 'damage' (a nil value) #1956
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1956
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
2022-05-21 16:28:10: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'petz' in callback luaentity_Punch(): ...5.5.1/Minetest_live/bin/../mods/petz/petz/misc/wagon.lua:17: attempt to perform arithmetic on local 'damage' (a nil value)
2022-05-21 16:28:10: ERROR[Main]: stack traceback:
2022-05-21 16:28:10: ERROR[Main]: ...5.5.1/Minetest_live/bin/../mods/petz/petz/misc/wagon.lua:17: in function 'func'
2022-05-21 16:28:10: ERROR[Main]: ...inetest_live/bin/../builtin/profiler/instrumentation.lua:107: in function <...inetest_live/bin/../builtin/profiler/instrumentation.lua:100>
Here's the original:
Here's my dumbfix:
@AliasAlreadyTaken any idea what triggered this?
Not the slightest. It hasn't happened ever since, my dumbfix isn't in the code anymore. I don't see why damage would ever become nil.
https://github.com/minetest/minetest/blob/master/doc/lua_api.txt#L2158
Except when something calls the function directly. Wouldn't such a direct call appear in stacktrace?
this was very much triggered by the engine, w/ the damage value being
nil
, and i don't understand how or why that would happen. as the dumbfix has been removed, and we've upgraded the engine, let's keep this issue open for the moment, and close after a couple months if it doesn't occur again.Let's do it the other way round: Close "cannot reproduce" and reopen when it occurs again. Because ... I will forget about this even tomorrow, let alone in a couple of month :D