1.1.116 #2637
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#2637
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?
Attention: 3d_armor was refactored, the armours are now independent mods. We need to enable all of those mods in world.mt and probably update dependencies
hm. i need to review what changes were made, this sounds like they did at least some of the things i wanted to do w/ 3d_armor
(adding this to my todo list just as a reminder to review the update)
reviewed, not particularly interesting. putting the actual armors into a separate mod from the API is reasonable, but there's no reason to add a separate "mod" for every armor... oh well.
not sure that enabling the armor mods in
world.mt
is enough, you might need to create anarmor.conf
file in the world root that defines the materials used in crafting them.Switch from tcp sockets to unix sockets. Example in testserver world.mt
Just in case there's no good option to do it before the next restart: Import #2803
Switch modstorage from file to sqlite:
2022-10-20 15:58:28: WARNING[Main]: Switching to SQLite3 is advised, please read http://wiki.minetest.net/Database_backends.
https://wiki.minetest.net/Database_backends#Mod_Storage_backend says
There is only ONE possible backend to migrate to. Would it have been so hard to give a reasonable example in that fabulous wiki??? Now I can only guess or make experiments. Is it "sqlite"? Or maybe "sqlite3"? Or "SQLite3" ???
=>
Same goes for the setting in world.mt, should this be sqlite, sqlite3 or SQLite3?
So, the right thing to do is NOT edit world.mt manually, but simply call
based on https://forum.minetest.net/viewtopic.php?p=408010#p408010
it should be "sqlite3"
not sure it's possible to do this easily, but if possible, could we keep the rollback logs until sometime after 1.1.116? there's still some stuff marsey seether griefed that i want to try to roll back w/ my custom command from the debuggery mod.
For context: Rollback database is 64 GB by now, in contrast to 105 GB of the main database. That's about two to three month of operation.
Rollbacks are stored in an sqlite database, no chance of concurrent access while the server is running.
I don't remove the rollback database too often, usually only during engine migrations.
However I'd like to have a feature in MT that let's me configure how long rollback entries are to be kept. Like "Cull all entries older than 3 Month" or so. For now, we can still do that when the server is not running by firing some SQL towards the rollback sqlite.
Regarding what MarseySeether did: We should add the debuggery mod until cleanup is done?
i would love that too, but no-one has done the work to "abstract" the rollback backend so that it could easily be ported to postgres. currently, it'd be a lot of work, i don't even see an open issue about it.
i don't understand?
Move all file regarding meseportals to the folder "meseportals"
Include somehow the watchtower functionality Ravise made: https://gitea.your-land.de/Ravise/watchtower
Another licensing confusion: Is BSD-3 compatible with MIT? Ravise especially stated he doesn't like MIT license in the commit messages. This website says it's more or less the same, but somehow one cannot be converted into the other: https://fossa.com/blog/open-source-software-licenses-101-bsd-3-clause-license/
#3013 depdendency circle
Switch to postgres 15 and tower-mod postponed, so we can close this.