Crash :-(

[VanessaE]

A user on my server caused this crash, while trying to dye some asphalt (which is not colorable) -- not in an owned area. This looks like an areas mod crash, so filing it here.

I suspect this has something to do with these various nil exceptions that have been added to Minetest/minetest_game recently.

2018-08-02 10:25:09: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod '' in callback item_OnUse(): Invalid position (expected table got nil).
2018-08-02 10:25:09: ERROR[Main]: stack traceback:
2018-08-02 10:25:09: ERROR[Main]:       [C]: in function 'get_areas_for_pos'
2018-08-02 10:25:09: ERROR[Main]:       .../.minetest/worlds/Building_World/worldmods/areas/api.lua:22: in function 'getAreasAtPos'
2018-08-02 10:25:09: ERROR[Main]:       .../.minetest/worlds/Building_World/worldmods/areas/api.lua:76: in function 'canInteract'
2018-08-02 10:25:09: ERROR[Main]:       ...etest/worlds/Building_World/worldmods/areas/interact.lua:4: in function 'is_protected'
2018-08-02 10:25:09: ERROR[Main]:       ...est/worlds/Building_World/worldmods/unifieddyes/init.lua:568: in function <...est/worlds/Building_World/worldmods/unifieddyes/init.lua:563>
2018-08-02 10:25:09: ERROR[Main]: stack traceback:
2018-08-02 10:25:09: ERROR[Main]:       [C]: in function 'get_areas_for_pos'
2018-08-02 10:25:09: ERROR[Main]:       .../.minetest/worlds/Building_World/worldmods/areas/api.lua:22: in function 'getAreasAtPos'
2018-08-02 10:25:09: ERROR[Main]:       .../.minetest/worlds/Building_World/worldmods/areas/api.lua:76: in function 'canInteract'
2018-08-02 10:25:09: ERROR[Main]:       ...etest/worlds/Building_World/worldmods/areas/interact.lua:4: in function 'is_protected'
2018-08-02 10:25:09: ERROR[Main]:       ...est/worlds/Building_World/worldmods/unifieddyes/init.lua:568: in function <...est/worlds/Building_World/worldmods/unifieddyes/init.lua:563>

[verymilan]

Similar here (i guess):

2018-10-26 11:34:35: ERROR[Main]: ServerError: AsyncErr: environment_Step: Runtime error from mod 'areas' in callback environment_Step(): Invalid float vector dimension range 'x' (expected -2.14748e+06 < x < 2.14748e+06 got -2.14748e+06).
2018-10-26 11:34:35: ERROR[Main]: stack traceback:
2018-10-26 11:34:35: ERROR[Main]:       [C]: in function 'get_areas_for_pos'
2018-10-26 11:34:35: ERROR[Main]:       ...a/.techeth/bin/../games/minetest_game/mods/areas/api.lua:6: in function 'getAreasAtPos'
2018-10-26 11:34:35: ERROR[Main]:       ...a/.techeth/bin/../games/minetest_game/mods/areas/hud.lua:10: in function <...a/.techeth/bin/../games/minetest_game/mods/areas/hud.lua:5>
2018-10-26 11:34:35: ERROR[Main]:       /home/illuna/.techeth/bin/../builtin/game/register.lua:412: in function </home/illuna/.techeth/bin/../builtin/game/register.lua:392>

[JurajVajda]

guess the same here:

2018-11-05 05:56:35: ERROR[Main]: ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod '' in callback on_playerReceiveFields(): Invalid float vector dimension range 'x' (expected -2.14748e+06 < x < 2.14748e+06 got 1e+20).
2018-11-05 05:56:35: ERROR[Main]: stack traceback:
2018-11-05 05:56:35: ERROR[Main]: 	[C]: in function 'get_areas_for_pos'
2018-11-05 05:56:35: ERROR[Main]: 	/root/.minetest/mods/areas/api.lua:22: in function 'getAreasAtPos'
2018-11-05 05:56:35: ERROR[Main]: 	/root/.minetest/mods/areas/api.lua:76: in function 'canInteract'
2018-11-05 05:56:35: ERROR[Main]: 	/root/.minetest/mods/areas/interact.lua:4: in function 'old_is_protected'
2018-11-05 05:56:35: ERROR[Main]: 	/root/.minetest/mods/basic_machines/protect.lua:12: in function 'is_protected'
2018-11-05 05:56:35: ERROR[Main]: 	/root/.minetest/mods/basic_machines/mover.lua:2508: in function 'func'
2018-11-05 05:56:35: ERROR[Main]: 	/usr/share/minetest/builtin/profiler/instrumentation.lua:106: in function </usr/share/minetest/builtin/profiler/instrumentation.lua:100>
2018-11-05 05:56:35: ERROR[Main]: 	/usr/share/minetest/builtin/game/register.lua:420: in function </usr/share/minetest/builtin/game/register.lua:400>

related? #27

[SmallJoker]

This is either an engine issue or a division error in a mod. Areas just happens to be a victim of this - all that could be done is to perform manual sanity checks.