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

testserver ts_furniture/init.lua:32: attempt to call method 'get_player_velocity' (a nil value) #5548

New Issue
Closed
opened 2023-11-23 21:17:01 +00:00 by AliasAlreadyTaken · 10 comments
AliasAlreadyTaken commented 2023-11-23 21:17:01 +00:00
Owner
Copy Link
2023-11-23 21:11:08: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod '' in callback environment_Step(): ...mt/5.7.0/Minetest_test/bin/../mods/ts_furniture/init.lua:32: attempt to call method 'get_player_velocity' (a nil value)
2023-11-23 21:11:08: ERROR[Main]: stack traceback:
2023-11-23 21:11:08: ERROR[Main]: 	...mt/5.7.0/Minetest_test/bin/../mods/ts_furniture/init.lua:32: in function 'on_rightclick'
2023-11-23 21:11:08: ERROR[Main]: 	/home/mt/5.7.0/Minetest_test/bin/../builtin/game/item.lua:313: in function 'on_place'
2023-11-23 21:11:08: ERROR[Main]: 	...mt/5.7.0/Minetest_test/bin/../mods/pipeworks/wielder.lua:439: in function 'act'
2023-11-23 21:11:08: ERROR[Main]: 	...mt/5.7.0/Minetest_test/bin/../mods/pipeworks/wielder.lua:126: in function 'wielder_on'
2023-11-23 21:11:08: ERROR[Main]: 	...mt/5.7.0/Minetest_test/bin/../mods/pipeworks/wielder.lua:162: in function 'action_on'
2023-11-23 21:11:08: ERROR[Main]: 	...Minetest_test/bin/../mods/mesecons/mesecons/internal.lua:193: in function <...Minetest_test/bin/../mods/mesecons/mesecons/internal.lua:186>
2023-11-23 21:11:08: ERROR[Main]: 	...etest_test/bin/../mods/mesecons/mesecons/actionqueue.lua:137: in function 'old_execute'
2023-11-23 21:11:08: ERROR[Main]: 	.../bin/../mods/mesecons_debug/overrides/mesecons_queue.lua:27: in function 'execute'
2023-11-23 21:11:08: ERROR[Main]: 	...etest_test/bin/../mods/mesecons/mesecons/actionqueue.lua:111: in function <...etest_test/bin/../mods/mesecons/mesecons/actionqueue.lua:73>
2023-11-23 21:11:08: 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>
``` 2023-11-23 21:11:08: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod '' in callback environment_Step(): ...mt/5.7.0/Minetest_test/bin/../mods/ts_furniture/init.lua:32: attempt to call method 'get_player_velocity' (a nil value) 2023-11-23 21:11:08: ERROR[Main]: stack traceback: 2023-11-23 21:11:08: ERROR[Main]: ...mt/5.7.0/Minetest_test/bin/../mods/ts_furniture/init.lua:32: in function 'on_rightclick' 2023-11-23 21:11:08: ERROR[Main]: /home/mt/5.7.0/Minetest_test/bin/../builtin/game/item.lua:313: in function 'on_place' 2023-11-23 21:11:08: ERROR[Main]: ...mt/5.7.0/Minetest_test/bin/../mods/pipeworks/wielder.lua:439: in function 'act' 2023-11-23 21:11:08: ERROR[Main]: ...mt/5.7.0/Minetest_test/bin/../mods/pipeworks/wielder.lua:126: in function 'wielder_on' 2023-11-23 21:11:08: ERROR[Main]: ...mt/5.7.0/Minetest_test/bin/../mods/pipeworks/wielder.lua:162: in function 'action_on' 2023-11-23 21:11:08: ERROR[Main]: ...Minetest_test/bin/../mods/mesecons/mesecons/internal.lua:193: in function <...Minetest_test/bin/../mods/mesecons/mesecons/internal.lua:186> 2023-11-23 21:11:08: ERROR[Main]: ...etest_test/bin/../mods/mesecons/mesecons/actionqueue.lua:137: in function 'old_execute' 2023-11-23 21:11:08: ERROR[Main]: .../bin/../mods/mesecons_debug/overrides/mesecons_queue.lua:27: in function 'execute' 2023-11-23 21:11:08: ERROR[Main]: ...etest_test/bin/../mods/mesecons/mesecons/actionqueue.lua:111: in function <...etest_test/bin/../mods/mesecons/mesecons/actionqueue.lua:73> 2023-11-23 21:11:08: 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> ```
TheMadModder commented 2023-11-23 21:19:14 +00:00
Copy Link

Was on test server working on projects. One being a deployer with a button on it. With a chair inside the deployer. I pressed the button and the chair was deployed. How ever the button stayed lit up and pressed down for 10 secondsish than the test server crashed. Will see if I can recreate this and will report more after this.

Was on test server working on projects. One being a deployer with a button on it. With a chair inside the deployer. I pressed the button and the chair was deployed. How ever the button stayed lit up and pressed down for 10 secondsish than the test server crashed. Will see if I can recreate this and will report more after this.
TheMadModder commented 2023-11-23 21:46:17 +00:00
Copy Link

I tested it a bunch of times differat setups and item. Finding that it seems to be due to the deployer duping items.

I tested it a bunch of times differat setups and item. Finding that it seems to be due to the deployer duping items.
AliasAlreadyTaken added the
1. kind/bug
 label 2023-11-23 22:06:12 +00:00
flux added the
3. source/mod upstream
3. source/integration
 labels 2023-11-23 23:49:25 +00:00
flux commented 2023-11-23 23:55:00 +00:00
Member
Copy Link

flux screams internally about the pipeworks fake player

on the other hand, i can't replicate this locally.

> flux screams internally about the pipeworks fake player on the other hand, i can't replicate this locally.
😆 1
flux commented 2023-11-23 23:56:53 +00:00
Member
Copy Link

the button stayed lit up and pressed down for 10 secondsish

because the server had already crashed at this point.

the deployer duping items

this is probably due to the on_place callback getting interrupted.

> the button stayed lit up and pressed down for 10 secondsish because the server had already crashed at this point. > the deployer duping items this is probably due to the `on_place` callback getting interrupted.
flux commented 2023-11-24 00:01:31 +00:00
Member
Copy Link

i think i'm going to PR pipeworks by implementing all the missing API stuff for the fake player. i'm sick of solving this problem in integration or by PR'ing abandoned mods.

i think i'm going to PR pipeworks by implementing all the missing API stuff for the fake player. i'm sick of solving this problem in integration or by PR'ing abandoned mods.
flux added the
2. prio/critical
 label 2023-11-24 00:01:41 +00:00
flux added this to the flux's TODO list project 2023-11-24 00:01:46 +00:00
flux self-assigned this 2023-11-24 00:01:51 +00:00
flux added the
4. step/at work
 label 2023-11-24 00:05:16 +00:00
flux commented 2023-11-24 00:09:56 +00:00
Member
Copy Link

this is probably due to the on_place callback getting interrupted.

nope, was because Parrish has the creative priv, so placing an item (even via a deployer) doesn't decrement the stack.

> this is probably due to the `on_place` callback getting interrupted. nope, was because Parrish has the creative priv, so placing an item (even via a deployer) doesn't decrement the stack.
flux commented 2023-11-24 21:04:23 +00:00
Member
Copy Link

upstream PR for pipeworks: https://github.com/mt-mods/pipeworks/pull/98

upstream PR for pipeworks: https://github.com/mt-mods/pipeworks/pull/98
flux added
4. step/blocked
 and removed
4. step/at work
 labels 2023-11-24 21:04:33 +00:00
flux added
4. step/ready to QA test
 and removed
4. step/blocked
 labels 2024-01-04 21:09:56 +00:00
flux commented 2024-01-04 21:10:35 +00:00
Member
Copy Link

the pipeworks PR got accepted, hopefully this will result in better compatibility with other mods

the pipeworks PR got accepted, hopefully this will result in better compatibility with other mods
AliasAlreadyTaken added this to the 1.1.123 milestone 2024-01-04 22:21:30 +00:00
AliasAlreadyTaken commented 2024-01-26 04:31:35 +00:00
Author
Owner
Copy Link

QA

I can neither reproduce the issue nor can I even get a chair into a deployer

QA I can neither reproduce the issue nor can I even get a chair into a deployer
AliasAlreadyTaken added the
ugh/QA main
 label 2024-01-26 04:31:42 +00:00
flux removed this from the flux's TODO list project 2024-03-28 23:44:14 +00:00
flux removed their assignment 2024-03-28 23:44:17 +00:00
flux added
5. result/fixed
 and removed
4. step/ready to QA test
 labels 2024-03-28 23:44:26 +00:00
flux commented 2024-03-28 23:44:53 +00:00
Member
Copy Link

i'm going to consider this fixed from two directions, even though we never had a repro. bench can go in a deployer, but no boom.

i'm going to consider this fixed from two directions, even though we never had a repro. bench can go in a deployer, but no boom.
flux closed this issue 2024-03-28 23:44:54 +00:00
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
1.1.123
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#5548
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?