Azelf reports: Crafting large quantities of i ... #3838
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3838
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?
Azelf reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i can't replicate this
mail to Azelf:
after talking w/ Azelf, i have a reliable replication:
see https://github.com/minetest-mods/crafting_bench/pull/9#discussion_r1090072884 for some discussion about what i think the problem is. caching craft results for unified_inventory_plus might make this go away, but that needs tested.
result of today's testing:
minetest.get_craft_result
can take up to .4 seconds locallygroup:...
items are in the recipe, the longer it takes, but this should be more thoroughly tested.register_craft
andclear_craft
while the server starts up, and replay that.upstream issue: https://github.com/minetest/minetest/issues/13231
upstream was closed in favor of an older issue, maybe related, maybe not: https://github.com/minetest/minetest/issues/11224
which now has an upstream PR: https://github.com/minetest/minetest/pull/13234
That's something I should compile into the testserver, right?
unless you think this is really urgent, let's wait until upstream gets merged. this is the sort of thing that should be dealt w/ in a few weeks, the fix is solid, but non-trivial.
this didn't make it into 5.7.0, which i assumed it would. this is a source of huge lag spikes, so probably we should patch this into our server. we need a process for adding cherry-picked commits to the server source code, i think.
the engine fix actually takes off about 15 seconds from my local server startup time (when unified_inventory initializes).
No longer facing these issues when crafting in bulk for a while now, so mark as closed?
hm. i feel like we should wait for the 5.8.0 release to close this, so we can use that as a base for future server builds instead of cherry-picked commits?
5.8.0 has been out for a bit, what's the plan?
running craft all w/ the example given doesn't lag the server to high heaven anymore.
hopefully sometime in the next week or so i'll get around to documenting all the issues that got fixed with 1.1.123. i'll close this then.
Please hold off on this one until we deliver 5.8.0
Now with 1.1.123 out, I'll focus on testing 5.8.0, on the testserver it's already running for a while. Plus, there may be commits we want to cherrypick from 5.9.0