is it the users are too dumb for the application, or the application isn't smart enough for the users?

more to the point, why is an informational stacktrace a default setting

if it's an error that the user should be concerned with, fine,

but that doesn't appear the norm.

As it it now, they seem like debug/trace logs.

#6694 is case in point

Top 2 pools are under 50% combined for the first time

minexmr 27.8%, nanopool 21.7%

It is in the *log*. The *log* is here to help debug.

Of course it's there by default, otherwise what's the point of it ?

Wiser words have never been said ^^^

"Hey guys, I got a bug" "Any interesting expcetions in the log ?" "Well, they aren't on by default, so I dunno"

That's what why it's on the INFO level.

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"

Maybe it is.

I'm not a fan of this. There's a already a couple of these things in IIRC.

hehehe

Meh, maybe.

yeah, i should make it a plugin

Danger: you are looking at debug logs. If you don't know what you are doing, piss off :D

well, noobs aren't gonna install plugins. I mean,

lol

No user serviceable parts inside. The user is not serviceable.

if you want to reduce those kind of bug reports, we can make the wall higher on github

i forget which repo it was,... but i went to file an issue, and there's this huge ass list of stuff needed etc

i said myself "i don't care this much" and moved on

so, you'd be filtering out people that may only give like 0.25 fucks.

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.

It's just that it's in a loop and super noisy, which is bloody annoying. That should be fixed.

I thought it was actually.

and i dunno why i like the idea of monerod trying to talk to you like a human

it kinda feels like one of those digital pets from the 90s

that exception is handled, not sure why it's necessary to log it?

s/Disk space is low/Meow! Meow! *scratches at the hard disk shop window*/

It logs all exceptions.

All exceptions are handled.

This one is just annoying because it's a common occurence.

it's handled inside librandomx

we could also disable hugepages for verification

but it takes the right amount of dumb to notice the error and not being able to enable hugepages at the same time

Maybe it could just disable all exception reporting coming from librandomx.

grep randomx in the trace, dump.

It'd hide any actual interesting one that might happen though.

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.

btw this monero-project/monero #6694 doesn't look like it's related to hugepages

[0x5651d8c98e6e]:_Z10setPagesRXPvm+0x4e) [0x5651d8c98e6e]

So this is useful to me to debug stuff in general.

setPagesRX is called in the JIT compiler to set the code executable if W^X is enabled

but we don't enable that by default

hm, we do.

fr verification anyway, not for mining

why are there two identical ifs?

looks like a previous step got deleted

there probably used to be another flag combo being tried with alloc_cache and we removed it

see an earlier version monero-project/monero dcea553#diff-a0882d2edfe5ec2ed6542d04307c946bR262

looks like hashrate is going crazy, there must be lotsa of the free audits currently running for the cloud providers :)

gethh 2 audits currently: xmr.nanopool.org/account/44BEHjxZWP…Fxr6GXjXtv1Dgovfm8UW8A5aFhv23BfLLjM

and xmr.nanopool.org/account/432xURdcG5…jPkzsFYKUz4ZgmvDp1CeX2eiGu511g5xWAG

107.7 MH/s and 125.6 MH/s

On the plus side, top 2 pools are still below 50% combined

so which other pools have grown?

nanopool

RespectXMR also got nice 60 MH/s

sounds about right. we were at 1.3GH before, now at 1.6GH

yes, pools and network hashrate are almost the same miningpoolstats.stream/monero

sech1 yep 0.25GH

tevador: how should I continue here? tevador/RandomX #183/files

AFAIK I have to inlcude #include <TargetConditionals.h> to differentiate between iOS / macOS

my new monero node soon :) => kobol.io

sech1 hyc can you please review also this? tevador/RandomX #187

selsta IIRC someone successfully built randomx for iOS here: tevador/RandomX #153