02:32:40 * gingeropolous blushes
03:07:22 <UkoeHB_> is it the users are too dumb for the application, or the application isn't smart enough for the users?
03:16:35 <jtgrassie> more to the point, why is an informational stacktrace a default setting
03:17:17 <jtgrassie> if it's an error that the user should be concerned with, fine,
03:17:35 <jtgrassie> but that doesn't appear the norm.
03:18:12 <jtgrassie> As it it now, they seem like debug/trace logs.
03:19:22 <jtgrassie> #6694 is case in point
05:26:44 <sech1> Top 2 pools are under 50% combined for the first time
05:26:58 <sech1> minexmr 27.8%, nanopool 21.7%
11:31:56 <moneromooo> It is in the *log*. The *log* is here to help debug.
11:32:07 <moneromooo> Of course it's there by default, otherwise what's the point of it ?
11:32:38 <sech1> Wiser words have never been said ^^^
11:32:40 <moneromooo> "Hey guys, I got a bug"  "Any interesting expcetions in the log ?"   "Well, they aren't on by default, so I dunno"
11:33:15 <moneromooo> That's what why it's on the INFO level.
11:49:52 <gingeropolous> I may edit the error message if I can navigate to that kind of error and make the text: "Hey! Thanks for reading your logs. The following output means blah, and nothing is actually broken"
11:50:29 <moneromooo> Maybe it is.
11:50:47 <moneromooo> I'm not a fan of this. There's a already a couple of these things in IIRC.
11:50:56 <gingeropolous> hehehe
11:51:13 <moneromooo> Meh, maybe.
11:51:18 <gingeropolous> yeah, i should make it a plugin
11:51:31 <moneromooo> Danger: you are looking at debug logs. If you don't know what you are doing, piss off :D
11:51:39 <gingeropolous> well, noobs aren't gonna install plugins. I mean,
11:51:40 <gingeropolous> lol
11:52:17 <moneromooo> No user serviceable parts inside. The user is not serviceable.
11:52:31 <gingeropolous> if you want to reduce those kind of bug reports, we can make the wall higher on github
11:52:49 <gingeropolous> i forget which repo it was,... but i went to file an issue, and there's this huge ass list of stuff needed etc
11:52:56 <gingeropolous> i said myself "i don't care this much" and moved on
11:53:21 <gingeropolous> so, you'd be filtering out people that may only give like 0.25 fucks.
11:53:23 <moneromooo> No. I like reports. It's just that reporting anything that you've not seen before is dumb. That particular user had a reason to though. randomx failed to allocate memory.
11:53:58 <moneromooo> It's just that it's in a loop and super noisy, which is bloody annoying. That should be fixed.
11:54:03 <moneromooo> I thought it was actually.
11:58:34 <gingeropolous> and i dunno why i like the idea of monerod trying to talk to you like a human
11:58:58 <gingeropolous> it kinda feels like one of those digital pets from the 90s
11:59:41 <tevador> that exception is handled, not sure why it's necessary to log it?
11:59:46 <moneromooo> s/Disk space is low/Meow! Meow! *scratches at the hard disk shop window*/
12:00:00 <moneromooo> It logs all exceptions.
12:00:16 <moneromooo> All exceptions are handled.
12:00:47 <moneromooo> This one is just annoying because it's a common occurence.
12:00:49 <tevador> it's handled inside librandomx
12:01:54 <tevador> we could also disable hugepages for verification
12:02:26 <tevador> but it takes the right amount of dumb to notice the error and not being able to enable hugepages at the same time
12:05:44 <moneromooo> Maybe it could just disable all exception reporting coming from librandomx.
12:06:02 <moneromooo> grep randomx in the trace, dump.
12:06:17 <moneromooo> It'd hide any actual interesting one that might happen though.
12:09:24 <moneromooo> For the record, the reason I added this is that we had a number of cases where users reported bugs where I wish I had known of exceptions happening and where.
12:09:28 <tevador> btw this https://github.com/monero-project/monero/issues/6694 doesn't look like it's related to hugepages
12:09:44 <tevador> [0x5651d8c98e6e]:_Z10setPagesRXPvm+0x4e) [0x5651d8c98e6e]
12:09:46 <moneromooo> So this is useful to me to debug stuff in general.
12:10:36 <tevador> setPagesRX is called in the JIT compiler to set the code executable if W^X is enabled
13:50:19 <hyc> but we don't enable that by default
13:51:54 <hyc> hm, we do.
13:52:37 <hyc> fr verification anyway, not for mining
14:06:47 <tevador> https://github.com/monero-project/monero/blob/master/src/crypto/rx-slow-hash.c#L224-L234
14:07:02 <tevador> why are there two identical ifs?
14:21:52 <hyc> looks like a previous step got deleted
14:24:06 <hyc> there probably used to be another flag combo being tried with alloc_cache and we removed it
14:33:48 <hyc> see an earlier version https://github.com/monero-project/monero/commit/dcea5536f09588a98f69a90124731bbf26b043f2#diff-a0882d2edfe5ec2ed6542d04307c946bR262
14:34:52 <gethh> looks like hashrate is going crazy, there must be lotsa of the free audits currently running for the cloud providers :)
15:56:13 <sech1> gethh 2 audits currently: https://xmr.nanopool.org/account/44BEHjxZWPFAY14Sen45qwShwX1m1RZw8FFgo9uY6A5FCnf3VBh7PS97Xr9FFxr6GXjXtv1Dgovfm8UW8A5aFhv23BfLLjM
15:56:18 <sech1> and https://xmr.nanopool.org/account/432xURdcG5af8j1bFNomb2ZruSMDcDrTLa7ePNxqgZsV5Vg3W61FpkgA8CmNjPkzsFYKUz4ZgmvDp1CeX2eiGu511g5xWAG
15:56:34 <sech1> 107.7 MH/s and 125.6 MH/s
16:12:27 <sech1> On the plus side, top 2 pools are still below 50% combined
16:13:52 <hyc> so which other pools have grown?
16:14:06 <sech1> nanopool
16:14:39 <sech1> RespectXMR also got nice 60 MH/s
16:35:10 <hyc> sounds about right. we were at 1.3GH before, now at 1.6GH
16:37:09 <sech1> yes, pools and network hashrate are almost the same https://miningpoolstats.stream/monero
16:41:44 <gethh> sech1 yep 0.25GH
18:23:43 <tevador> https://github.com/tevador/RandomX/pull/189
18:56:13 <selsta> tevador: how should I continue here? https://github.com/tevador/RandomX/pull/183/files
18:56:25 <selsta> AFAIK I have to inlcude #include <TargetConditionals.h> to differentiate between iOS / macOS
18:58:12 <gethh> my new monero node soon :) => https://kobol.io/
21:52:50 <tevador> sech1 hyc can you please review also this? https://github.com/tevador/RandomX/pull/187
21:55:18 <tevador> selsta IIRC someone successfully built randomx for iOS here: https://github.com/tevador/RandomX/issues/153