Time Nick Message 01:28 MTDiscord Hello core developers, you might want to voice your opinion on https://github.com/orgs/community/discussions/159749 because this would make it so you have to deduce more rambling hallucinated nonsense than you already do 02:04 MTDiscord It's pretty easy to make commercial llms like copilot expose themselves by just telling it, on it's honor, to swear that it is a biological human, and that falsifying the statement would be a sever ethical standard violation. 02:08 MTDiscord Yes. But, the issue is not in that you can use AI to generate a completely garbage issue. The issue is that it will be a standard little button on the issue reporter which is a one click slop generator 03:10 [ the solution is to move away from github already 10:09 rubenwardy Will flatpak migrate saved data with the EoL migration thing? 10:39 MTDiscord "Flatpak will prompt the user when updating or installing whether they want to migrate to the new ID. Any data managed by Flatpak will also be migrated automatically on entering yes." 10:39 MTDiscord https://docs.flathub.org/docs/for-app-authors/maintenance#end-of-life-rebase 10:39 sfan5 has someone uploaded devtest to CDB? 10:46 MTDiscord it's still on 5.10.0 it seems 10:47 MTDiscord i don't think i have access though, i'm not a maintainer, and i don't know the password of the luanti account 10:47 sfan5 neither do I 10:50 [MatrxMT] jordan4ibanez: as a triager the last thing I want is to deal with effortlessly autogenerated code, so +1. Relevant: https://github.com/dotnet/runtime/pull/115762#issuecomment-2898635945 10:57 MTDiscord As long as the issues / PRs are properly marked as autogenerated, while annoying, it should be bearable; and probably even automatable. 12:26 MTDiscord Cc @rollerozxa update devtest 12:26 rubenwardy Added you both as maintainers on devtest 12:37 MTDiscord wsor: done, uploaded both for 5.11 and 5.12 12:42 MTDiscord because devtest is inside of the larger engine repo it's not really possible to have it automatically make releases using just the git integration that CDB provides. but maybe @Luanzai could be able to make a separate repo mirror of it that slices the devtest game into its own repo and tags when stable releases happen, similar to what he's done with individual MTG mods: https://github.com/minetest-game 12:43 MTDiscord (obviously devtest would remain in the engine repo, this would just be as a convenience for us on the CDB side, like how the separate sethome mod package on CDB is sourced from here) 12:54 sfan5 would be nice if someone could review #16158 12:54 ShadowBot https://github.com/luanti-org/luanti/issues/16158 -- [no sq] Do not allow vector components to be nil or NaN + unit tests by sfan5 12:58 sfan5 should the pattern VoxelArea(bp1 * MAP_BLOCKSIZE, (bp2+1) * MAP_BLOCKSIZE - v3s16(1)) get a helper macro/function? it appears countless of times 13:03 rubenwardy You could use GitHub Actions to push devtest to CDB on release 13:03 rubenwardy but imo devtest shouldn't be aiming for end users, so doesn't make much sense for CDB 13:03 rubenwardy should have a modpack on top of void game for modders 14:26 SFENCE_arch From the opposite side, unittest fails without devtest. So should we release Luanti without or with limited unittests? 14:58 MTDiscord We should release Luanti without unit tests and without devtest. 15:06 MTDiscord the only reason I would see an end user running unit tests would be linux distributions during a check test in their packaging process. and in that case they would likely be running the tests with the built engine still contained within the source tree before the installation/packaging process occurs, so devtest would be available for them 15:09 MTDiscord related: we should make unit tests a separate executable 15:09 MTDiscord I was about to ask if that were the consensus 😄 it seems like it is 15:55 MTDiscord small type fixes updated to 5.12.0 and ready to merge! https://github.com/luanti-org/luanti/compare/master...proller:minetest:minetest32net?expand=1 15:56 MTDiscord lol 15:56 MTDiscord https://cdn.discordapp.com/attachments/747163566800633906/1376227339553476608/image.png?ex=68348f16&is=68333d96&hm=a04ba0e1851592025f720fcdf6bc3e33afc1265dce16d66582628eb8a202cdbc& 15:58 MTDiscord no problem to merge master it anyone ready to push merge button 16:52 SFENCE rebase, and PR have to be reviewed and approved first. 17:18 MTDiscord i rebase it almost every year 17:45 SFENCE And do you have opened PR for it? I do not remember seeing it. 17:50 MTDiscord https://github.com/luanti-org/luanti/pull/11843 17:50 MTDiscord https://github.com/luanti-org/luanti/pull/11910 17:50 MTDiscord https://github.com/luanti-org/luanti/pull/12142 20:16 MTDiscord getting world expansion for 5.13 would be awesome 20:18 sfan5 won't happen 20:18 MTDiscord Proller doesnt seem to agree, maybe we should clarify why 20:21 MTDiscord Is it a "we dont have the resources to review it that quickly" or a "we refuse to merge this feature"? 20:24 sfan5 out of those two it's the latter. we decided in a meeting that this isn't on the roadmap and we won't spend time on it 20:26 MTDiscord sfan5: The roadmap is due for a review now 20:26 sfan5 I predict it will not be on it even after the review 20:26 MTDiscord https://github.com/luanti-org/luanti/issues/16162 20:27 MTDiscord Is there a concrete reason why it isnt on the roadmap? 20:27 MTDiscord (or wont be considered, ever) 20:28 rubenwardy the roadmap is just a docment to make developer consensus more visible. If multiple developers agree they want to do something, it can be on the roadmap. So the core issue is getting multiple core devs to prioritise this 20:28 sfan5 https://irc.luanti.org/minetest-dev/2022-04-10#i_5959102 feel free to read 20:29 MTDiscord I am unclear on the 3-part situation: Are all the PRs necessary, or is just the 3rd? Is it that the first 2 break compatibility temporarily until the 3rd is merged? 20:29 rubenwardy I personally wouldn't review such a thing - my focus is on UI, mainmenu, and steam deck (ie: gamepads) 20:29 rubenwardy not that I have much time for LT at all 20:31 MTDiscord Well, no one ever said it was likely. Just possible. Remotely possible. 20:33 MTDiscord first part - changing s16 type to pos_t (by default pos_t is s16 and nothing brokes) 20:34 MTDiscord second - on top of first part, change float to opos_t (still by default nothing broken) 20:36 MTDiscord third part - adding compatibility with old clients, still can be merged without enabling s32 and broking anything 20:38 MTDiscord so it should be merged first without any type change, just type aliases