Time  Nick          Message
04:46 hmmmm         PTAL https://github.com/kwolekr/minetest/commit/18e0f1f24fb78a228afa837c7358dcb3737b0d03
04:47 hmmmm         (note that this commit doesn't actually add any functionality; it's the piece of the threaded lua feature that's most vulnerable to merge conflicts)
09:57 PilzAdam      https://github.com/PilzAdam/minetest/commit/6907c3e40a16d491fd0f7b224ba30a58e0777a24
09:58 hmmmm         oops
09:59 hmmmm         looks good to me I guess
10:00 PilzAdam      I'll merge it in a few minutes then
10:54 BlockMen      can i merge #3209 ?
10:54 ShadowBot     https://github.com/minetest/minetest/issues/3209 -- Add option to disable backface culling for models by BlockMen
10:54 BlockMen      *after adding documentation
11:00 VanessaE      BlockMen: HybridDog makes a good point in there:  can something be added to allow backface culling to be selectively en/disabled for mesh nodes also?
11:00 VanessaE      (it supposedly works if you use special_materials, but that option doesn't work for mesh nodes)
11:01 BlockMen      VanessaE,  its optional and enabled by default, which mean it is only disabled when wanted
11:01 BlockMen      thats why it says "add option" ;)
11:02 VanessaE      hm, ok.  tried to read through the code but it didn't look like it was operating on mesh nodes.  rather, just CAOs
11:02 BlockMen      oh, misread
11:02 BlockMen      sry
11:03 VanessaE      sorry, I meant "mesh nodes" as modders use the phrase :)
11:03 BlockMen      umm...yes, it could i think . but how is that releated to this pull?
11:03 VanessaE      i.e. stairs
11:03 VanessaE      well I consider it related in that it's backface culling :)
11:04 BlockMen      well, but complete different area, so nothing to be added in this pull. but make an issue for it if you think it is needed ;)
11:05 VanessaE      meh
11:06 VanessaE      well anyway, +1 if that fixes the issue :)
11:15 BlockMen      added paramat to Developer group at forums and removed RBA and darkrose since they are not core members anymore
11:53 VanessaE      something really needs to be done about this crash-on-exit shit
11:53 VanessaE      particularly crash-on-exit-to-menu -- often either MT just exits, or it hangs and has to be kill -9'd
11:54 nrzkt         sfan5: http://servers.minetest.net/
11:54 nrzkt         i think there is a problem, no ?
11:54 sfan5         indeed
12:11 BlockMen      nrzkt, sfan5: #3209 ?
12:11 ShadowBot     https://github.com/minetest/minetest/issues/3209 -- Add option to disable backface culling for models by BlockMen
12:11 BlockMen      can i merge it?
12:12 sfan5         yep
12:12 BlockMen      thanks
12:13 sfan5         nrzkt: ipv4 announcing went poof
12:14 VanessaE      guess I should be glad my servers can do ipv6 also :P
12:14 nrzkt         sfan5, ok
12:15 sfan5         i have no idea how this happend
12:15 sfan5         and restarting nginx & uwsgi does not fix it
12:15 nrzkt         an IPv4 routing problem with the server provider ?
12:16 sfan5         GET /list works over IPv4
12:16 sfan5         GET /announce just causes nginx not to respond with anything at all
15:15 PilzAdam      est31, https://github.com/minetest/minetest/commit/6907c3e40a16d491fd0f7b224ba30a58e0777a24 run updatepo.sh again
15:16 est31         updatepo.sh is evil, it bloats the repo size
15:17 PilzAdam      how much?
15:17 est31         don#t know
15:17 est31         lemme get an upper border for the size
15:17 PilzAdam      this are 10 translation lines changed
15:18 est31         the problem aren't those lines
15:18 est31         the problem is that updatepo.sh is non-deterministically ordered
15:18 est31         idk what they've thought when they wrote it
15:19 est31         you run updatepo.sh
15:19 est31         you commit
15:19 est31         you run it again
15:19 est31         and volia, a huge diff is there!
15:19 est31         reordering everything
15:20 est31         okay, the diff is 201k, if you gzip its 31k
15:21 est31         so there is an xgettext command to somehow sort
15:21 PilzAdam      what if you use --sort-output instead of --sort-by-file for msgmerge?
15:22 est31         we use msgmerge?
15:22 est31         we dont use that
15:22 est31         but xgettext has a similar command
15:22 est31         it will rip stuff out of context however
15:22 PilzAdam      https://github.com/minetest/minetest/blob/master/util/updatepo.sh#L70
15:22 est31         why can't they first sort by file, then sort by output?
15:25 est31         look at the top commit here https://github.com/est31/minetest/commits/master
15:25 est31         dont open it in github
15:25 est31         rather wget https://github.com/est31/minetest/commit/e53af96cc65cc06ea6fbe0e15deb0ce5384a228d.patch
15:25 est31         then git am e53af96cc65cc06ea6fbe0e15deb0ce5384a228d.patch
15:27 PilzAdam      it seems to reorder the commented-out old stuff
15:27 PilzAdam      we could just remove that?
15:28 est31         we could
15:29 est31         lets do the following
15:29 est31         I write a bug report for the msgmerge list
15:29 est31         then we hope for an answer
15:30 est31         if its not there within a week, we do the updatepo
15:30 est31         and remove the comments
15:30 est31         if ther is an answer, we wonder when it can be fixed
15:31 est31         and if that is inside a reasonable time frame, we wait till then, and I install a fixed msgmerge
15:31 PilzAdam      sounds good, I guess
15:54 VanessaE      what does this mean?  http://pastebin.ubuntu.com/12946053/
15:54 VanessaE      (starting at line 94)
15:57 kahrl         VanessaE: note the pos = {X = -21474836, ...}
15:57 kahrl         there's an object out of bounds
15:57 VanessaE      eek
15:58 est31         a player, it is
15:59 est31         player name not known
15:59 VanessaE      how the hell is that even possible? O_o
16:01 est31         dunno
16:01 est31         but it should have saved the coords in the player file
16:02 est31         so you can find out the name if you look at the players at the server atm
16:02 est31         perhaps the player had teleport, then its even harder to detect
16:02 VanessaE      no one has teleport on that server, except admins
16:03 est31         well, then I guess it has been created by manual flying
16:03 est31         perhaps automated with a hacked client
16:03 est31         idk
16:03 est31         or the less exciting version, some internal error
16:03 est31         you know, which set the player coord to that pos
16:03 kahrl         I've heard of users getting randomly teleported to insane coordinates which historically led to error messages by the audio subsystem
16:04 ElectronLibre Sometimes player can get out of bounds, I've seen that multiple times. Usually it's triggered when they join the server.
16:04 VanessaE      no player file matches grep "214748" *
16:04 kahrl         never experienced it myself, so I assume it's a rogue mod
16:06 ElectronLibre VanessaE: It might be written as a power of 10.
16:07 VanessaE      nothing comes up among the server's files when I search 4748 either
16:07 VanessaE      (nothing relevant anyway)
16:08 kahrl         perhaps a mod passes in a huge number somewhere and the lua_api cpp code converts it to s32
16:08 kahrl         which results in (s32)-0x80000000, as I noted in #3237
16:08 ShadowBot     https://github.com/minetest/minetest/issues/3237 -- PseudoRandom always generating same sequence with big seed
16:08 kahrl         and -0x80000000 is -2147483648
16:09 VanessaE      there are only two mods on the server that can teleport -- the "spawn" mod, and Sokomine's travelnet
16:09 VanessaE      pretty sure the former isn't using coords even remotely similar :)
16:20 est31         oh, I have an idea
16:24 VanessaE      ?
16:25 est31         for the msgmerge problem
16:27 VanessaE      bbl
16:47 PilzAdam      est31, yes?
16:48 est31         http://stackoverflow.com/questions/8219900/filtering-a-diff-with-a-regular-expression
16:49 est31         and made to ignore all lines starting with #~
16:49 est31         and the other question: http://stackoverflow.com/questions/13192594
16:50 PilzAdam      what if the #~ lines are actually changed? e.g. if new ones are added, or old ones deleted?
16:50 est31         yup, thats the problem
16:51 PilzAdam      you'd have to only ignore the lines, that are in both parts of the patch (old and new)
16:51 PilzAdam      maybe cut the #~ lines, run updatepo.sh, and the append them again?
16:52 PilzAdam      or would that just eliminate the whole purpose of them?
16:53 est31         sort of yes.
16:53 est31         'll include that in the email
16:55 est31         ok mail sent
17:16 BlockMen      PTAL at https://github.com/BlockMen/minetest/commit/eb92bfb03038aa2ed42af46ff5ec7d144f0ff9af
17:20 est31         +1
17:20 est31         BlockMen, ^
17:22 BlockMen      ok, pushing
18:14 PilzAdam      https://github.com/PilzAdam/minetest/commit/eba5f7cd6cfb550b28de230bd5013a771d37b196
18:15 est31         ++
18:16 Krock         &= 0x00    >:)
18:46 PilzAdam      merging now
22:05 paramat       if no objections will merge game#713 soon
22:05 ShadowBot     https://github.com/minetest/minetest_game/issues/713 -- Default/functions: ABM for moss growth on cobble near water by paramat
23:09 paramat       now merging game 713
23:14 paramat       done
23:23 paramat       hmmmm just so you know, i'll start work on adding rotation support to simple decorations, just the 4 rotations around y-axis and random, as with schematic decorations
23:23 est31         PTAL https://github.com/est31/minetest/commit/d0a37365f045cdb8d84eacec2790339c5821b2c0
23:26 BlockMen      est31 why you want print() be logged?
23:27 est31         often it contains important information, no?
23:27 BlockMen      i use it to debug without spamming my log
23:27 BlockMen      if i want have it be logged just use minetest.log()
23:27 BlockMen      im not happy with that change
23:28 est31         hrmmm
23:28 est31         well, good to know that
23:28 est31         it was needed for the ncurses console patch, and I've thought I commit these two unrelated things so that the commit doesnt bloat
23:29 BlockMen      just my opinion. if others think more your way fine aswell, then i will just use my costum builtin
23:29 est31         bc if normal print is used, it translates to printf, which then makes the console.... become inconsistent
23:29 est31         its really not nice ux wise to have something printed
23:29 est31         there is a way however to fulfill your wish, even with the console
23:30 est31         that however is closely tied to how the console works, so better done in my pr itself
23:30 est31         well, I'll remove the print redefine, is the commit then ok?
23:31 BlockMen      sure
23:40 BlockMen      oh, loglevel null, ... nvm
23:40 BlockMen      est31 ^
23:41 est31         null doesnt exist
23:41 est31         there is none
23:41 est31         but none != null xD
23:44 BlockMen      haarspalterei
23:45 est31         what about it?
23:45 est31         <BlockMen> oh, loglevel null, ... nvm
23:47 BlockMen      i withdraw my objection against print() override. and since you knew what i ment with loglevel null your comment was haarspalterei :P