AliasAlreadyTaken reports: testserver smartshops facing e ... #4257
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4257
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?
AliasAlreadyTaken reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
it looks fine on the test server to me currently? and i can't reproduce it locally? do you know which version of the smartshop code was present before and after this issue?
For 1.1.118 I rolled back to 0997e9f1cda6d4f0af111ff5f2bf5389d6303cd8 which does not cause the issue. During testing it was on latest master:
40481067f2
w/ 0997e9f1cda6d4f0af111ff5f2bf5389d6303cd8:
w/ 40481067f2e08890a0017d47624b1b7ba2bb5573:
i'm stumped.
latest commit is bd33fb9c910573f2c88efba3c177e390bfca3c6a
And the oddly oriented smartshops are back.
Since you mentioned it I added
a53bf1df96
but they're still oriented wrong on the testserver
could you leave them on the testserver for the moment, so i can take a look at them and see if i can learn anything?
@AliasAlreadyTaken i still can't replicate this locally (i thought maybe the issue was run-once LBMs but that's not it).
but perhaps try testing this commit to see whether the problem goes away? the test would have to be against a fresh clone of the world from production.
also, i presume that you don't copy the world via postgres DB commands and not via minetest schemas? https://github.com/minetest/minetest/pull/13432
We dump the database and restore it via postgresql.
Ok, I'll add this commit. But why is it on the AiTechEye/smartshop repo? :D
Sounds like when I comment out this code, I could omit the lbm altogether? At least in flux/smartshop commit bd33fb9c910573f2c88efba3c177e390bfca3c6a there is nothing else in there?
I didn't import a new database, but looked at cities I was fairly certain they were not loaded yet: Pluton and Monsabor. Both had their smartshops turned.
This is the commit after which the smartshops are turn:
2b037300be
In the commit before they are not.
hm. does the behavior of 4dir vary by server? O_O.
try this?
76bbc6a8f9
4dir is a 5.7.0 thing. YL is on 5.6.1
Try search 4dir on the API doc:
https://raw.githubusercontent.com/minetest/minetest/587f6656a4b86346e35da1b43b48b832d3f1b32e/doc/lua_api.txt
running dev?
80574cdbe8
might be the culpriti did not realize it was that new. alright, that's certainly the cause then.
We'll test for 5.7.0 right after 1.1.119
Edit: If you want to write code for engine versions < 5.7.0 we'll test it for 5.6.1, if not we'll postpone delivery until we get 5.7.0
We rolled it back to what it was before. I'll remove this from the 1.1.119 milestone and readd to the milestone after the 5.7.0 rollout.
But now for reals: your-land/minetest-smartshop#24
this is live