| Time |
Nick |
Message |
| 00:12 |
MTDiscord |
<luatic> I think we should split our issue forms up along the lines of "graphical issue" which should force you to mention all the current details in the issue and "normal issue" which shouldn't |
| 01:21 |
|
TheCoffeMaker joined #minetest-dev |
| 04:00 |
|
MTDiscord joined #minetest-dev |
| 04:33 |
|
whosit joined #minetest-dev |
| 04:44 |
|
YuGiOhJCJ joined #minetest-dev |
| 07:07 |
|
cranezhou joined #minetest-dev |
| 07:14 |
|
SFENCE_arch joined #minetest-dev |
| 09:22 |
|
Warr1024 joined #minetest-dev |
| 09:37 |
|
SFENCE_arch joined #minetest-dev |
| 09:47 |
|
Warr1024 joined #minetest-dev |
| 13:48 |
Krock |
will merge #15365 #15364 #15368 #15372 in 20 minutes |
| 13:48 |
ShadowBot |
https://github.com/minetest/minetest/issues/15365 -- Apply "and" to server list & content search terms by appgurueu |
| 13:48 |
ShadowBot |
https://github.com/minetest/minetest/issues/15364 -- Fix model[] being lit wrongly if shaders are disabled by appgurueu |
| 13:48 |
ShadowBot |
https://github.com/minetest/minetest/issues/15368 -- JsonCPP: restore '1.0.0+' compatibility by SmallJoker |
| 13:48 |
ShadowBot |
https://github.com/minetest/minetest/issues/15372 -- replace occurences of 'forum.minetest.net' with 'forum.luanti.org' by veprogames |
| 14:03 |
|
AliasAlreadyTake joined #minetest-dev |
| 14:07 |
Krock |
merging |
| 14:11 |
Krock |
done |
| 14:15 |
|
Noisytoot joined #minetest-dev |
| 15:07 |
MTDiscord |
<luatic> good |
| 15:09 |
MTDiscord |
<luatic> i think maybe we should have something like a rejected label for #15208? "won't add / won't fix" don't cut it, the fundamental issue should be fixed, but not like this. i suppose "won't add" would work, but is intended for feature requests, not bugfix PRs. |
| 15:09 |
ShadowBot |
https://github.com/minetest/minetest/issues/15208 -- add_area_node_boxes: Cap number of ignore node boxes considered to avoid memory exhaustion by goodspeed34 |
| 15:10 |
[MatrxMT] |
<Zughy> I don't think it's necessary, it sounds like more work for triagers. Just use one of the two labels |
| 15:12 |
[MatrxMT] |
<Zughy> Actually, you don't need any. Roadmap is clear, just close it |
| 15:12 |
[MatrxMT] |
<Zughy> Oh nvm, I was looking at the wrong one. One of the two labels then |
| 15:59 |
|
Desour joined #minetest-dev |
| 16:16 |
Desour |
why is dedicated_server_step max 1 sec? |
| 16:16 |
Desour |
>:( always that unnecessary limits |
| 16:18 |
|
nrz joined #minetest-dev |
| 16:31 |
MTDiscord |
<luatic> Desour: I didn't know we had partially implemented #15219 already, now we just gotta make it configurable ;-) |
| 16:31 |
ShadowBot |
https://github.com/minetest/minetest/issues/15219 -- Configurable max dtime |
| 16:34 |
Krock |
How many random settings do we want? Yes. |
| 16:34 |
Desour |
that issue is not about the setting. I'm speaking about the maximum for the minimum <`_´> |
| 16:37 |
MTDiscord |
<luatic> oh yeah. though frankly, a server step > 1s doesn't make sense, and a bit of idiot proofing is always a good idea. |
| 16:38 |
MTDiscord |
<luatic> Krock: I don't think the setting requested by Warr would be random, I think it'd be quite a good addition. The engine can't make a sensible tradeoff in general here. |
| 16:41 |
MTDiscord |
<luatic> I'll look into fixing collisions the proper way. |
| 16:41 |
Krock |
An easier solution would be to have a fixed ceiling of N seconds for any physics-related calculations (which already exists). |
| 16:41 |
Krock |
Configuring this simply means that the server is overloaded. Either due to inefficient mods or inefficient engine functions. |
| 16:42 |
MTDiscord |
<luatic> Krock: I don't think this should be restricted to physics or engine physics in particular. |
| 16:42 |
MTDiscord |
<luatic> "Losing time" generally and "falling behind" consistently is much more sensible. |
| 16:43 |
Krock |
Right. Delaying ABMs (which already happens) is also an approach to spread the load. |
| 16:44 |
MTDiscord |
<luatic> For ABMs we should really rework the scheduler to spread them better, Warr has another issue for that. |
| 16:45 |
Desour |
Krock: oh so abms are delayed to a later step if the current one already took too long? |
| 16:46 |
Krock |
Desour: #8645 from my faith memory |
| 16:46 |
ShadowBot |
https://github.com/minetest/minetest/issues/8645 -- Improve ABM time budget handling. by lhofhansl |
| 16:47 |
Desour |
ah I see. thx! |
| 16:47 |
Krock |
I searched for issues but apparently this PR came before the complaint |
| 16:48 |
Krock |
nvm here's one #6928 |
| 16:48 |
ShadowBot |
https://github.com/minetest/minetest/issues/6928 -- Smoother ABM throttling |
| 16:49 |
Krock |
open PRs, not issues 8) |
| 16:58 |
Desour |
hm, so if the 200ms budget is reached, abms with fast interval essentially run less often |
| 17:05 |
Krock |
it affects all ABMs, but the mapblocks are picked at random |
| 17:09 |
Desour |
oops right |
| 17:12 |
|
SFENCE joined #minetest-dev |
| 18:17 |
|
markwiemer joined #minetest-dev |
| 18:17 |
sfan5 |
found a 7 year old bug \o/ |
| 18:18 |
MTDiscord |
<wsor4035> which one? 😛 |
| 18:18 |
markwiemer |
I remember encountering a bug that was opened before I was born, back in my Java Swing days |
| 18:19 |
|
markwiemer left #minetest-dev |
| 18:19 |
sfan5 |
nobody has noticed because it's inconsequential |
| 18:19 |
|
markwiemer joined #minetest-dev |
| 18:26 |
|
markwiemer joined #minetest-dev |
| 18:28 |
|
Noisytoot joined #minetest-dev |
| 18:29 |
sfan5 |
pushing https://github.com/minetest/minetest/commit/294a30e445ec9cd94d66efc8f94048606716ad35 after CI has passed |
| 20:56 |
|
SFENCE joined #minetest-dev |
| 21:19 |
|
SFENCE joined #minetest-dev |
| 21:52 |
|
zayd joined #minetest-dev |
| 22:09 |
|
SFENCE joined #minetest-dev |
| 22:42 |
|
SFENCE joined #minetest-dev |
| 23:15 |
|
SFENCE joined #minetest-dev |
| 23:32 |
|
panwolfram joined #minetest-dev |
| 23:43 |
|
SFENCE joined #minetest-dev |
