chesttools crash #4641
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4641
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?
whosit wrote on the other page:
for reference, passing the position of a node like that in a formspec is considered an antipattern, see https://forum.minetest.net/viewtopic.php?t=19129
Heh, found this much older closed issue that seems to be the same too:
#506 (comment)
this is fixed upstream, but not in yl_stable.
This fix:
c851ab7e16
It will prevent crash, but players will still be able to fiddle with
pos
field...For the time being I added the fix of
c851ab7e16
Apparently my dumbfix disabled pipeworks functionality. Now the bugfix was added temporarily to yl_commons until it is fixed upstream
What exactly is the repro here? I tried to tab out of the "name" field, but cannot reproduce the issue atm?
from above,
if that's not crashing the server now, we should consider the upstream fix to be live.