your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.4k Projects 2 Wiki

Runtime error from mod 'worldedit_commands' in callback on_chat_message(): std::bad_array_new_length #2701

New Issue
Open
opened 2022-09-17 01:30:30 +00:00 by AliasAlreadyTaken · 3 comments
AliasAlreadyTaken commented 2022-09-17 01:30:30 +00:00
Owner
Copy Link

I tried to copy a region with worldedit.

//1
//2
//save t2

At this point I didn't read properly and thought the area was copied already, so I wen to a new spot very far away and tried to insert the area:

//1
//load t2

It did not work ofc, because there was no t2.we created in the first place. In the chat I found a mesage asking along the lines of "You sure?? That's a lot of blocks. If you really want, do //y". So I did

//y

Which resulted in:

2022-09-17 01:21:06: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'worldedit_commands' in callback on_chat_message(): std::bad_array_new_length
2022-09-17 01:21:06: ERROR[Main]: stack traceback:
2022-09-17 01:21:06: ERROR[Main]: 	[C]: in function 'read_from_map'
2022-09-17 01:21:06: ERROR[Main]: 	...test/bin/../mods/Minetest-WorldEdit/worldedit/common.lua:53: in function 'keep_loaded'
2022-09-17 01:21:06: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit/serialization.lua:57: in function 'serialize'
2022-09-17 01:21:06: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:1379: in function 'func'
2022-09-17 01:21:06: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:48: in function 'callback'
2022-09-17 01:21:06: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit_commands/safe.lua:30: in function 'func'
2022-09-17 01:21:06: ERROR[Main]: 	...inetest_test/bin/../builtin/profiler/instrumentation.lua:107: in function 'worldedit_command_y'
2022-09-17 01:21:06: ERROR[Main]: 	...itAdditions/worldeditadditions_core/core/safe_region.lua:36: in function 'func'
2022-09-17 01:21:06: ERROR[Main]: 	/home/mt/5.6.0/Minetest_test/bin/../builtin/game/chat.lua:79: in function 'func'
2022-09-17 01:21:06: ERROR[Main]: 	...inetest_test/bin/../builtin/profiler/instrumentation.lua:107: in function <...inetest_test/bin/../builtin/profiler/instrumentation.lua:100>
2022-09-17 01:21:06: ERROR[Main]: 	.../mt/5.6.0/Minetest_test/bin/../builtin/game/register.lua:429: in function <.../mt/5.6.0/Minetest_test/bin/../builtin/game/register.lua:415>
I tried to copy a region with worldedit. //1 //2 //save t2 At this point I didn't read properly and thought the area was copied already, so I wen to a new spot very far away and tried to insert the area: //1 //load t2 It did not work ofc, because there was no t2.we created in the first place. In the chat I found a mesage asking along the lines of "You sure?? That's a lot of blocks. If you really want, do //y". So I did //y Which resulted in: ``` 2022-09-17 01:21:06: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'worldedit_commands' in callback on_chat_message(): std::bad_array_new_length 2022-09-17 01:21:06: ERROR[Main]: stack traceback: 2022-09-17 01:21:06: ERROR[Main]: [C]: in function 'read_from_map' 2022-09-17 01:21:06: ERROR[Main]: ...test/bin/../mods/Minetest-WorldEdit/worldedit/common.lua:53: in function 'keep_loaded' 2022-09-17 01:21:06: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit/serialization.lua:57: in function 'serialize' 2022-09-17 01:21:06: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:1379: in function 'func' 2022-09-17 01:21:06: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:48: in function 'callback' 2022-09-17 01:21:06: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit_commands/safe.lua:30: in function 'func' 2022-09-17 01:21:06: ERROR[Main]: ...inetest_test/bin/../builtin/profiler/instrumentation.lua:107: in function 'worldedit_command_y' 2022-09-17 01:21:06: ERROR[Main]: ...itAdditions/worldeditadditions_core/core/safe_region.lua:36: in function 'func' 2022-09-17 01:21:06: ERROR[Main]: /home/mt/5.6.0/Minetest_test/bin/../builtin/game/chat.lua:79: in function 'func' 2022-09-17 01:21:06: ERROR[Main]: ...inetest_test/bin/../builtin/profiler/instrumentation.lua:107: in function <...inetest_test/bin/../builtin/profiler/instrumentation.lua:100> 2022-09-17 01:21:06: ERROR[Main]: .../mt/5.6.0/Minetest_test/bin/../builtin/game/register.lua:429: in function <.../mt/5.6.0/Minetest_test/bin/../builtin/game/register.lua:415> ```
AliasAlreadyTaken added the
3. source/mod upstream
 label 2022-09-17 06:35:45 +00:00
flux commented 2022-09-17 18:01:36 +00:00
Member
Copy Link

there are at least 2 bugs here

  1. worldedit shouldn't crash the server by trying to emerge an area that's too large to fit in memory
  2. redefining //1 and //2 should clear the previous action for which //y is pending
there are at least 2 bugs here 1. worldedit shouldn't crash the server by trying to emerge an area that's too large to fit in memory 2. redefining `//1` and `//2` should clear the previous action for which `//y` is pending
flux added the
2. prio/critical
 label 2022-09-22 23:46:39 +00:00
flux added the
1. kind/bug
 label 2022-11-07 17:22:31 +00:00
flux added a new dependency 2022-11-07 17:23:09 +00:00
your-land/administration#178 - interactive volumes
AliasAlreadyTaken commented 2023-12-05 13:49:26 +00:00
Author
Owner
Copy Link

Issue still happens:

2023-12-05 13:44:21: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'worldedit_commands' in callback on_chat_message(): std::bad_array_new_length
2023-12-05 13:44:21: ERROR[Main]: stack traceback:
2023-12-05 13:44:21: ERROR[Main]: 	[C]: in function 'read_from_map'
2023-12-05 13:44:21: ERROR[Main]: 	...test/bin/../mods/Minetest-WorldEdit/worldedit/common.lua:53: in function 'keep_loaded'
2023-12-05 13:44:21: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit/serialization.lua:57: in function 'serialize'
2023-12-05 13:44:21: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:1434: in function 'func'
2023-12-05 13:44:21: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:50: in function 'callback'
2023-12-05 13:44:21: ERROR[Main]: 	...n/../mods/Minetest-WorldEdit/worldedit_commands/safe.lua:32: in function 'func'
2023-12-05 13:44:21: ERROR[Main]: 	...inetest_test/bin/../builtin/profiler/instrumentation.lua:108: in function 'func'
2023-12-05 13:44:21: ERROR[Main]: 	/home/mt/5.7.0/Minetest_test/bin/../builtin/game/chat.lua:79: in function </home/mt/5.7.0/Minetest_test/bin/../builtin/game/chat.lua:52>
2023-12-05 13:44:21: ERROR[Main]: 	.../mt/5.7.0/Minetest_test/bin/../builtin/game/register.lua:446: in function <.../mt/5.7.0/Minetest_test/bin/../builtin/game/register.lua:432>

Upstream issue: https://github.com/Uberi/Minetest-WorldEdit/issues/234

Issue still happens: ``` 2023-12-05 13:44:21: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'worldedit_commands' in callback on_chat_message(): std::bad_array_new_length 2023-12-05 13:44:21: ERROR[Main]: stack traceback: 2023-12-05 13:44:21: ERROR[Main]: [C]: in function 'read_from_map' 2023-12-05 13:44:21: ERROR[Main]: ...test/bin/../mods/Minetest-WorldEdit/worldedit/common.lua:53: in function 'keep_loaded' 2023-12-05 13:44:21: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit/serialization.lua:57: in function 'serialize' 2023-12-05 13:44:21: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:1434: in function 'func' 2023-12-05 13:44:21: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit_commands/init.lua:50: in function 'callback' 2023-12-05 13:44:21: ERROR[Main]: ...n/../mods/Minetest-WorldEdit/worldedit_commands/safe.lua:32: in function 'func' 2023-12-05 13:44:21: ERROR[Main]: ...inetest_test/bin/../builtin/profiler/instrumentation.lua:108: in function 'func' 2023-12-05 13:44:21: ERROR[Main]: /home/mt/5.7.0/Minetest_test/bin/../builtin/game/chat.lua:79: in function </home/mt/5.7.0/Minetest_test/bin/../builtin/game/chat.lua:52> 2023-12-05 13:44:21: ERROR[Main]: .../mt/5.7.0/Minetest_test/bin/../builtin/game/register.lua:446: in function <.../mt/5.7.0/Minetest_test/bin/../builtin/game/register.lua:432> ``` Upstream issue: https://github.com/Uberi/Minetest-WorldEdit/issues/234
flux commented 2023-12-20 20:50:34 +00:00
Member
Copy Link

additional upstream issue for //1///2 resetting pending actions requiring approval https://github.com/Uberi/Minetest-WorldEdit/issues/236

additional upstream issue for `//1`/`//2` resetting pending actions requiring approval https://github.com/Uberi/Minetest-WorldEdit/issues/236
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Depends on
You do not have permission to read 1 dependency
Reference: your-land/bugtracker#2701
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?