Minetest logo

IRC log for #minetest-dev, 2024-11-27

| Channels | #minetest-dev index | Today | | Google Search | Plaintext

All times shown according to UTC.

Time Nick Message
00:00 MTDiscord <luatic> Maybe interesting idea: Add instrumentation to get_objects_inside_radius to sample some query times. This could be probabilistic for minimal overhead. We could also track some stats (how many entities these return on average, how many calls are made per step on average, etc.)
00:05 Eragon joined #minetest-dev
00:44 Noisytoot joined #minetest-dev
00:49 MTDiscord <exe_virus> Looks like there's a setting to dump them to the log interval, all good
00:51 MTDiscord <exe_virus> That said, I do like the idea of better profiling tooling in general, will research what's easy, I know we have that Lua jit profiler working now, and can get solid flame graphs data, just need to package it all nicely
04:00 SFENCE joined #minetest-dev
04:04 v-rob joined #minetest-dev
05:00 MTDiscord joined #minetest-dev
05:51 SFENCE joined #minetest-dev
07:08 SFENCE joined #minetest-dev
08:38 SFENCE joined #minetest-dev
08:38 YuGiOhJCJ joined #minetest-dev
09:55 SFENCE joined #minetest-dev
10:22 hwpplayer1 joined #minetest-dev
11:05 Thomas-S joined #minetest-dev
11:05 Warr1024 joined #minetest-dev
11:05 m42uko_ joined #minetest-dev
11:05 basxto joined #minetest-dev
11:11 SFENCE joined #minetest-dev
11:19 YuGiOhJCJ joined #minetest-dev
12:22 SFENCE joined #minetest-dev
13:06 MTDiscord <josiah_wi> Does anyone run Minetest on Haiku anymore? We have support for it in the build, which implies we should be testing it.
13:26 sfan5 we can't test everything we have theoretical support for
13:31 MTDiscord <josiah_wi> But you're paying for that support with build complexity.
13:32 MTDiscord <josiah_wi> You're paying and you don't even know whether it works.
13:33 MTDiscord <josiah_wi> The macro that the build sets is deprecated, and I was going to follow the compiler's recommendation to replace it with a different macro, but now I'm questioning whether the macro is even necessary at all. There's no way to find out probably without attempting the build on a Haiku system.
13:33 MTDiscord <josiah_wi> I'll leave it be for now.
13:38 SFENCE joined #minetest-dev
13:40 sfan5 which macro?
13:45 MTDiscord <josiah_wi> The _BSD_SOURCE macro for glibc feature testing. The compiler recommends to replace it with _DEFAULT_SOURCE, but that macro has slightly different behavior, so we're not guaranteed 100% that it won't introduce an issue, I think.
13:45 sfan5 uh, does haiku even use glibc?
13:46 MTDiscord <josiah_wi> Maybe whatever it uses alse has a _BSD_SOURCE? Maybe it's not deprecated on whatever it uses, then. I wouldn't spend too much time on it. There are other things that are much easier to test.
13:46 sfan5 yeah
13:58 SFENCE joined #minetest-dev
14:37 Desour joined #minetest-dev
15:14 SFENCE joined #minetest-dev
15:43 v-rob joined #minetest-dev
15:49 qur joined #minetest-dev
16:07 v-rob joined #minetest-dev
16:33 v-rob joined #minetest-dev
16:39 SFENCE joined #minetest-dev
16:59 SFENCE joined #minetest-dev
17:22 grorp joined #minetest-dev
17:22 SFENCE joined #minetest-dev
17:23 Krock Will merge #15415 #15466 #15477 in 15 minutes
17:23 ShadowBot https://github.com/minetest/minetest/issues/15415 -- Add `core.spawn_tree_on_vmanip` by cx384
17:23 ShadowBot https://github.com/minetest/minetest/issues/15466 -- Main menu: Fix server selection by appgurueu
17:23 ShadowBot https://github.com/minetest/minetest/issues/15477 -- Network: Fix serialization version checks by SmallJoker
17:26 Krock ignore the first. will re-review later.
17:34 Sokomine joined #minetest-dev
17:39 SFENCE joined #minetest-dev
17:40 Krock done
17:42 SFENCE_ joined #minetest-dev
17:43 qur joined #minetest-dev
18:55 SFENCE joined #minetest-dev
19:02 SFENCE joined #minetest-dev
19:11 v-rob joined #minetest-dev
20:48 v-rob joined #minetest-dev
21:22 pgimeno_ joined #minetest-dev
23:33 panwolfram joined #minetest-dev

| Channels | #minetest-dev index | Today | | Google Search | Plaintext