02:38:17 <jberman[m]> to be clear, my "yep" was to kayaba's explanation. every view tag is independent and is constructed on a per-output basis. even if 2 outputs have the same view tag, it doesn't yield any useful about the outputs, it's just random chance. a single wallet can create a view tag of any value between 0 and 255 for each output when constructing a tx (each view tag in the tx is independent), and a wallet still has to check every single view tag
02:38:18 <jberman[m]> when scanning
02:45:33 <nantuk[m]> Hi there! Does anyone know if there is any software that can scan every new block and tell me if there is any output (with amount) going to a list of subaddresses I provide (along with the primary address and view key related to them)?
02:45:33 <nantuk[m]> Reading the docs, I see it can be done with wallet-cli (to create wallet file restoring from primary address and view key) and wallet-rpc  (to open and close wallet and get txs). But as I want to automate this, I would need to have one wallet-rpc running for each primary address, and query all of them every minute. It don't think it will work with 1k addresses
02:56:02 <ofrnxmr[m]> Perhaps monero-lws
02:57:49 <ofrnxmr[m]> I havent played with it extensively, but it does scan multiple address and view key pairs.
02:57:49 <ofrnxmr[m]> But its meant to be used with wallets. I imagine there to be some functionality to parse the data without a wallet
02:59:34 <jberman[m]> It doesn't support subaddresses yet
03:10:46 <nantuk[m]> Thanks, I'll take a look at it
03:29:08 <jberman[m]> here's the current proposal to support subaddresses in monero-lws/light wallet servers in general; I think that would enable exactly what you're looking for: https://github.com/monero-project/meta/pull/647
09:39:21 <rbrunner> Was there a large testnet reorg in the last few days?
09:40:32 <rbrunner> With "large" meaning 1005 blocks or something similarly dramatic?
09:41:05 <rbrunner> Or maybe a fork of testnet which one of my daemons chased down for that many blocks?
09:42:51 <sech1> I synced testnet two days ago and I don't see any reorgs in the log
09:49:29 <rbrunner> Hmmm, strange.
09:50:34 <rbrunner> My situation: I have two machines where I claim that testnet is running identically, daemon just compiled from master just this morning, and synced to top of testnet without problems
09:50:49 <rbrunner> I have a wallet that opens and refreshed without problems on one computer
09:51:13 <rbrunner> On the other it balks and tells me it wants to do a reorg 1005 blocks deep which is larger than the allowed maximum
09:52:14 <rbrunner> Currently out of ideas where the difference and/or the problem could be :)
10:48:47 <rbrunner> I found a little more: Running daemon and monero-wallet-cli without any special options beside "--testnet" works
10:50:31 <rbrunner> If I bind the daemon to the static public IP of the machine like so: monerod --testnet --rpc-bind-ip <ip number> --confirm-external-bind
10:51:17 <rbrunner> And then instruct the wallet to use that like so: ./monero-wallet-cli --testnet --daemon-address <ip number>:28081
10:52:21 <rbrunner> Then the wallet reacts with, probably expected: Warning: using an untrusted daemon at 80.254.179.107:28081
10:53:22 <rbrunner> But also gives an unexpected error:
10:53:24 <rbrunner> Error: refresh failed: refresh error: reorg exceeds maximum allowed depth, use 'set max-reorg-depth N' to allow it, reorg depth: 520. Blocks received: 0
10:54:24 <moneromooo> Possibly there is a reorg, but a smaller one ? When using an untrusted daemon, the wallet quantizes its current height, so will request earlier blocks.
10:54:51 <moneromooo> (so a daemon cannot tell a returning wallet from that info)
10:56:40 <rbrunner> Not sure I understand what you mean. The wallet is currently synced to almost top of chain, the daemon follows the chain normally
10:56:53 <rbrunner> The wallet misses only a few blocks now
10:57:12 <rbrunner> Where would a reorg sneak in here?
10:58:42 <sech1> I always add --trusted-daemon when I connect to my nodes
10:59:06 <Stnby[m]> Hello, is Monero Wallet RPC thread safe? Or should the RPC calls be synchronous?
10:59:30 <sech1> it should be thread safe
11:01:34 <moneromooo> I mean that the wallet will pretend its height, when starting is something like H - H % 1024 or so.
11:01:57 <moneromooo> So if it needs to reorg for, say, 5 blocks, it might end up asking for 1005 blocks.
11:02:27 <rbrunner> Yeah, but why should that be suddenly a problem?
11:02:29 <moneromooo> I think the wallet RPC is thread safe because it handles one connection at a time.
11:02:47 <moneromooo> Because there might be a reorg.
11:03:13 <Stnby[m]> But it's single threaded right?
11:03:22 <moneromooo> Try "status" in the wallet. It might give you a block hash.
11:03:35 <rbrunner> I narrowed down further: The external IP seems to play no role, simply telling the CLI the daemon is untrusted triggers my problem
11:03:39 <rbrunner> like so: ./monero-wallet-cli --untrusted-daemon --testnet
11:03:45 <moneromooo> Yes, "one connection at a time" implies that, for "interesting" threads.
11:04:01 <Stnby[m]> I tried hitting the wallet rpc with multiple parallel requests and shit went wrong
11:04:43 <moneromooo> OK, that's odd. Maybe someone made it handle several calls at once then. Pretty sure there's a comment in hte source saying "don't do that".
11:04:47 <Stnby[m]> Then I decided to make it synchronous which seemed to behave better
11:05:39 <rbrunner> Another wallet wants to go back 153 blocks now, and again tells that this is too much.
11:07:06 <Siren[m]> Stnby[m]: Seems like a lot of rpc binding libs allow this to happen, we should probably place those mutexes in our lib to make it safe
11:07:55 <rbrunner> A third one 898.
11:08:09 <rbrunner> How could they all hit the same reorg problem?
11:08:36 <moneromooo> Did you use them all at about the same time ?
11:08:48 <rbrunner> Probably not, no
11:08:58 <moneromooo> How probably ?
11:09:07 <rbrunner> I check
11:09:23 <moneromooo> Within a day or so of each other.
11:10:28 <rbrunner> No. I guess that also the reason they all want to go back a different number of blocks.
11:10:44 <rbrunner> Because their caches do stand at different heights now
11:10:59 <rbrunner> One is almost at top, the other two different numbers of weeks back
11:11:04 <moneromooo> The comment's still there about threads. Maybe the underlying code now does a listen/accept/handoff which would be unfortunate. I don't think it's super likely though. So maybe the problem is elsewhere...
11:11:57 <moneromooo> Did you run these wallets off a temporarily branched chain (ie, when using --fixed-difficulty etc for testing) ?
11:12:27 <rbrunner> No, and they still sync properly, I just have to leave out " --untrusted-daemon" for the CLI wallet ...
11:13:35 <moneromooo> Did you keep the old caches ?
11:13:52 <rbrunner> Probably could fish them out of some backup.
11:14:18 <moneromooo> Then change "status" or other to print the height and hash of the top block they have. Compare with the chain.
11:14:40 <moneromooo> If it's on the chain, it looks like a bug. If it's not on the chain, it looks like a reorg.
11:15:18 <moneromooo> print_block in monerod remembers old orphans, usually.
11:15:28 <rbrunner> I synced now one wallet to top, without " --untrusted-daemon ". Started again with " --untrusted-daemon ", and now it want to reorg 555 deep.
11:15:49 <moneromooo> All my alt chains are 1 block long. Very nice...
11:16:06 <moneromooo> Then it is almost certainly a bug.
11:16:09 <rbrunner> Somebody around with current master compiled who could check running the CLI wallet with " --untrusted-daemon " with that, with any wallet?
11:16:35 <rbrunner> I have done a lot of dumb things in the last 5 years of Monero, who knows :)
11:17:18 <sech1> I confirm  https://p2pool.io/u/4daa3896be2dbbc1/fail.png 
11:17:38 <rbrunner> Ok, so it's not me.
11:17:52 <sech1> It works perfectly fine with --trusted-daemon
11:17:54 <rbrunner> Can somebody please inform the CEO?
11:18:03 <rbrunner> Monero is broken :)
11:18:23 <sech1> BTW I'm testing p2pool + testnet right now - https://github.com/SChernykh/p2pool/issues/153
11:18:25 <moneromooo> If it's only a problem with untrusted nodes, it's not a problem :)
11:18:31 <rbrunner> Lol
11:18:33 <sech1> so I have the wallet and testnet node at hand
11:18:37 <moneromooo> But still, I'll try to have a look.
11:19:18 <moneromooo> Are you looking at it sech1 ?
11:19:46 <alexanarcho[m]> Are there any devs in here that have experience with monero-javascript?
11:20:12 <sech1> Reorg error? No, I have no idea what to look at.
11:20:25 <moneromooo> OK, I will then.
11:20:26 <sech1> Plus I have to go now
11:21:06 <sech1> I'm testing p2pool during testnet fork
11:58:21 <moneromooo> rbrunner: https://github.com/monero-project/monero/pull/8331
11:58:45 <moneromooo> (tests not run yet, but I don't expect they'll fail (but then I never do))
12:00:35 <rbrunner> Thanks, that was fast. Is this an old error then, nothing to do with recent changes?
12:00:44 <moneromooo> Since 2020 I think.
12:00:55 <moneromooo> So not too recent, but not too old.
12:01:41 <rbrunner> I wonder why I only hit that today. Before I was probably using an early 0.17 version.
12:02:25 <moneromooo> Maybe because you usually use your local node ?
12:03:21 <moneromooo> You could bisect I guess, maybe something else "hid" this before.
12:03:34 <rbrunner> I caused that "untrusted" situation on my Monerotech.info webwallet by using the external IP maybe starting 1 year ago.
12:04:03 <rbrunner> Anyway, I will try the fix.
12:04:16 <sech1> Already fixed? Nice
12:09:52 <rbrunner> Works.
12:44:53 <moneromooo> Looks like it already broke right after the patch in 2020.
12:45:21 <moneromooo> That might mean close to nobody uses untrusted nodes :)
12:45:38 <moneromooo> Or, more likely, people mindlessly add --trusted-node for those.
12:45:54 <moneromooo> Or just stop using monero.
12:46:02 <sech1> I admit I do this:P
12:46:10 <moneromooo> Stop using monero ? :D
12:46:30 <sech1> Add --trusted-node. But I run my own nodes 
12:46:52 <plowsof[m]> in wownero cli it makes you pass "--this-is-a-malicious-spyware-node" before adding any remote node 
12:47:20 <moneromooo> Sounds like something I'd add.
12:49:24 <moneromooo> UkoeHB: do you have a prefered wording for "multisig is disabled, enable with set x=1" ?
13:10:52 <alt-web> i'm working on a monero node running on kicksecure (https://kicksecure.com) on top of a debian 11 vps... you guys have a great day
13:19:43 <AmeyaDeshmukh[m]> Hey! Want to start contributing to/working on projects in the space. I'm a  CS sophomore in India good with C, C++ and Rust. Do tell me where and how I can start!
13:25:01 <alt-web> very possible... i am a web designer, system admin, highly skilled in html/css, bash scripting, and gimp
13:28:30 <moneromooo> You can look around at what floats your boat. There's monero, the GUI, mymonero, monero-lws, haveno, and more.
13:28:49 <moneromooo> C/C++ means monero I guess.
13:30:11 <moneromooo> If you want to hack on monero itself, it's easy: biuld the source, use it, find something that's a bit broken, not good enough, etc, that annoys you, and fix/improve it.
13:30:59 <moneromooo> I suggest minimal changes (ie, no reformatting or changes just because you like it better the new way). Separate patches by self contained change if possible.
13:31:01 <AmeyaDeshmukh[m]> Nice! Will do that. Any other projects using a C/C++ codebase other than Monero core?
13:31:16 <moneromooo> There's a CONTRIBUTING.md file with that kind of guidelines.
13:31:33 <moneromooo> The GUI has some C++, but it's mostly boilerplate IIRC. The meat is JS.
13:31:44 <moneromooo> monero-lws is also C++.
13:31:49 <AmeyaDeshmukh[m]> Yep got it. Hack around and find out and if I get a solution worth implementing at scale with proper security (with no reformatting or major changes), submit a PR?
13:32:06 <moneromooo> Right.
13:32:29 <AmeyaDeshmukh[m]> Great, that works very well. Thank you. 🙏
13:32:57 <moneromooo> Major changes is fine once you're comfortable with the code. It's more like... no unnecessary changes.
13:33:32 <moneromooo> Especially the "my editor reformatted the whole file" nightmare :D
13:34:08 <AmeyaDeshmukh[m]> Will take some time to get comfortable with the code itself. Still in the learning process, but enjoying every bit due to the community. Probably the first time I've seen non gatekept research unlike universities etc where you require credentials
13:34:13 <moneromooo> You can also look at github for issues, see if one of them looks easy and something you'd want to work on.
13:34:24 <AmeyaDeshmukh[m]> moneromooo: Haha! Definitely not :D
13:35:19 <AmeyaDeshmukh[m]> moneromooo: Don't necessarily need easy. Willing to be a long term contributor and grind on the problem if it has the potential to teach me a lot!
13:36:04 <moneromooo> Well, you gotta start with easy bits. I did.
13:36:36 <moneromooo> If you don't, you run the risk of losing interest.
13:36:43 <moneromooo> Up to you of course.
13:37:23 <AmeyaDeshmukh[m]> Oh! Would love to hear your journey if you could elaborate :)
13:38:00 <moneromooo> Well... I just wanted to contribute, so I looked at something easy to start with, that's all.
13:38:19 <moneromooo> I read code, and I found something that looked buggy, if memory serves.
13:38:31 <moneromooo> So I patched it. Hopefully less buggy now.
13:39:18 <moneromooo> And as I read code, I got more comfortable with it, what's where, what does what, etc. Allowing me to work on more complex stuff.
13:39:29 <moneromooo> Pretty standard really.
13:39:54 <alt-web> i'm learning python now, to create gui front-ends for running bash script... the masses need the gui... make it very pretty in gimp... large scale adoption is the key for monero's future... payment interfaces running as apps on mobile
13:40:34 <quila[m]> Anyone managed to statically build monero, with `BUILD_GUI_DEPS` on?
13:40:37 <moneromooo> Ah. I used to dream of some generic GUI maker that'd run --help on programs and auto generate a GUI from that.
13:40:44 <quila[m]> On mac m1*.
13:42:13 <selsta> quila[m]: what are you trying to do?
13:42:56 <alt-web> a generic gui maker... interesting to say the least 
13:43:53 <quila[m]> selsta: I am want to build `libwallet_merged.a`. I managed to do in on Big Sur, but since Monterey I could not do it anymore.
13:43:54 <moneromooo> Pipe dream I think. You'd end up with something verbose and not really usable in practice.
13:44:37 <selsta> quila[m]: did you test release-v0.17 or master branch?
13:44:39 <moneromooo> Paste errors to paste.debian.net and post the URL here.
13:46:25 <quila[m]> selsta: Yes, I have. 
13:46:38 <quila[m]> moneromooo: Sure, let me grab the logs.
13:46:46 <selsta> I mean which branch did you test? both?
13:46:46 <moneromooo> Which of the two ?
13:47:08 <selsta> there were some changes in master branch a while ago
13:47:21 <alt-web> true... a gui for me is python executing script, nice logo, minimal, very clean css interface
13:47:31 <quila[m]> I usually just do with the release branch, sorry.
13:47:58 <moneromooo> It's fine. That branch ought to build.
13:48:58 <quila[m]> I have also tried to change the arch to `apple-latest`/`apple-a14`/`apple-m1`.
13:49:17 <quila[m]> Let build it again to share the logs.
13:51:44 <quila[m]> selsta: do you run `make release-static` or `release-static-mac-x86_6` to build on M1? (btw I tried both)
13:52:15 <quila[m]> Monero builds nicely, only GUI_DEPS on causes the error.
13:54:30 <alt-web> on another tip... i created my first nft, sized for a twitter banner, as the musk-rat bought twitter and only a matter of time before nft format allowed as banner images there... going price: 10 xmr ;) made a screenshot and put up on one of my web pages if anyone wants to see it... very colorful :) https://alt-web.xyz/
13:56:01 <quila[m]> <moneromooo> "Paste errors to paste.debian.net..." <- There you go: https://paste.debian.net/1240950/
13:57:24 <moneromooo> The error seems to be: clang: error: the clang compiler does not support '-march=x86-64'
13:57:28 <quila[m]> If I build it with arch `apple-latest` it can make it to 50% or somthing.
13:57:34 <moneromooo> Unlcear where from due to -j10.
13:57:51 <moneromooo> Can you try with -j1 so we see where it comes from ?
13:58:23 <baro77[m]> <moneromooo> "There's a CONTRIBUTING.md file..." <- I guess this: https://github.com/monero-project/monero-site/blob/master/CONTRIBUTING.md
13:58:52 <moneromooo> I don't see anything setting x86-64 specifically for GUI deps.
13:59:04 <quila[m]> moneromooo: Sure. Do you want me to change the arch to `apple-latest` also?
13:59:20 <quila[m]> Or just same command?
13:59:31 <moneromooo> Try same for now.
14:00:43 <quila[m]> moneromooo: https://paste.debian.net/1240953/
14:00:44 <moneromooo> Hmm. Looking at the Makefile, release-static does assume x86_64.
14:01:03 <moneromooo> Doesn't explain why the rest of moneor would build though.
14:01:04 <quila[m]> Yes...
14:01:42 * quila[m] sent a code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/2336b4f7377a45e5042f6a74106a0550a0eb589d
14:01:50 <selsta> I don't use release-static on Mac
14:02:10 <moneromooo> Fails in the first file with the "top level" biuld system. You sure the rest of monero built ?
14:02:27 <quila[m]> These are the archs I got.
14:02:29 <moneromooo> Oh, maybe only with apple-latest then ? If so, try with apple-latest nw please.
14:03:06 <moneromooo> apple-m1 seems nice too.
14:03:21 <moneromooo> Or you could wait for hyc, who built for m1, I never did so I'm blind here.
14:03:40 <selsta> You can set ARCH=default
14:07:49 <quila[m]> Weird, I don't know what I did overnight but none of those are progressing now.
14:07:56 <quila[m]> Same error.
14:08:15 <quila[m]> Let me try `apple-a14` and `default`.
14:08:27 <moneromooo> You might need to remove CMakeCache.txt from your build tree, cmake is a bit of an ass when it comes to changing settings.
14:08:30 <quila[m]> ```clang: error: the clang compiler does not support '-march=apple-m1'```
14:08:46 <moneromooo> Try default or native then as selsta said.
14:09:22 <moneromooo> When you have something working, a new make target for M1 can be added :)
14:12:12 <quila[m]> `default` seems to have gone through. 50% now.
14:19:16 <quila[m]> moneromooo: it failed at 92% https://paste.debian.net/1240955/
14:21:29 <moneromooo> Looks like it just needs extra libs to link against.
14:21:39 <quila[m]> How this `default` works behind the scenes? It seems to corresponds to `arm64`.
14:21:42 <moneromooo> EVP_MD_size sounds like openssl.
14:21:53 <moneromooo> event_* is probably libevent
14:22:27 <moneromooo> sech1: you had the libevent problem recently, no ? Fixed it ?
14:28:47 <quila[m]> Building it with `native` results in the same error: https://paste.debian.net/1240960/
14:32:30 <quila[m]> My libevent to have been built on `arm64`. Same for openssl.
14:33:00 <selsta> quila[m]: did you install it with homebrew?
14:33:18 <quila[m]> selsta: Yes...
14:36:55 <quila[m]> Just to clarify, I have managed to build this in the past on Mac x64 Big Sur. It has then failed on mac x64 Monterey and now M1 Monterey.
14:37:52 <quila[m]> I even innocently copied the `.dylib` from the old machine to this one but it seems Rosetta don't like it.
14:38:18 <selsta> You might have to compile static openssl yourself? Not sure.
14:40:04 <quila[m]> I do have the openssl static libs:
14:40:04 <quila[m]> ```/opt/homebrew/opt/openssl@3/lib/libssl.dylib: Mach-O 64-bit dynamically linked shared library arm64```
14:40:30 <quila[m]> (static lib is also here, just can't run `file` on it)
14:40:33 <selsta> try to install openssl⊙1
14:40:44 <quila[m]> Let me try that.
14:41:56 <selsta> and remove @3
14:45:38 <quila[m]> Ok, I am building now with openssl1.1.
14:50:33 <sech1> moneromooo I fixed it by compiling on another machine (I was able to fix libevent undefined symbols, but there was another library that gave linker errors)
14:51:05 <sech1> nettle library: undefined reference to `nettle_rsa_public_key_init' and so on
14:53:53 <quila[m]> <selsta> "and remove @3" <- Same error: https://paste.debian.net/1240964/
14:54:07 <quila[m]> sech1: are you on M1?
14:54:34 <sech1> no, it was an Ubuntu x64 VM
14:58:37 <quila[m]> Hummm... It seems I will have to investigate further. If anyone if manages to build statically with `BUILD_GUI_DEPS` ON on M1 chip let me know. I will do the same if I find out.
14:59:48 <quila[m]> Not sure if anyone from cake wallet is in the room.
15:01:21 <quila[m]> That could help*
15:02:33 <selsta> and compiling without build_gui_deps works?
15:03:00 <quila[m]> selsta: Yes, it does.
15:12:26 <moneromooo> That IS really odd since build_gui_deps is just an extra wallet lib. The binaries get build regardless.
15:16:51 <selsta> quila[m]: how did you enable build_gui_depy?
15:18:05 <quila[m]> selsta: I updated the line 1244 of CMakeLists.
15:22:15 <selsta> can you double check by setting it to OFF on line 1244 to see if it compiles?
15:25:30 <quila[m]> Sure, doing it now.
15:31:40 <quila[m]> Ok, I get the same error. With `BUILD_GUI_DEPS` OFF. It seems it just `STATIC=ON` related. moneromooo sorry for the misleading info earlier, I probably ran some other command.
15:33:40 <moneromooo> Yes, I can totally see that static would do that.
15:34:09 <moneromooo> So you just need to find out what static libs link to those libs that aren't linked in.
15:35:28 <quila[m]> I ran `debug-static-all` and got same problem: https://paste.debian.net/1240968/
15:35:42 <moneromooo> Then detect and add them to the link line, either through the lib that depend on them (ie, if libX wants libY, detect libY and "set X_LIBRARY $X_LIBRARY $Y_LIBRARY" or so) or through EXTRA_LIBRARIES if it's "most programs need that system lib", like librt, libdl etc.
15:36:18 <moneromooo> For an example of this, see how libpgm is detected and added to libzmq, since libzmq is sometimes built with pgm support.
15:36:39 <moneromooo> That's why pkg-config was made, but cmake NIH obviously.
15:37:22 <quila[m]> It seems I don't have `nghttp2` installed on my machine.
15:37:35 * quila[m] sent a monero code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/375a9f4e5d648f157ce187d9b9ad4a368774d72f
15:39:11 <moneromooo> You can add it to the deps list in README.md. If there's none for Mac yet, you can add it.
15:40:22 <quila[m]> Hopefully it's just that. Do you recognize `_event_base_dispatch` function?
15:40:53 <moneromooo> Likely libevent/libevent2/
15:40:56 <quila[m]> Or any of these:```undef: _event_base_set... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/92bf5cacfb623643414859e13430380778de573d)
15:41:18 <moneromooo> grep in /usr/include (or wherever on mac)
15:44:00 <quila[m]> Ok, I can see problems here.
15:44:08 * quila[m] sent a code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/5233628d4f8b51c300f624aec776d64a4da7884f
15:44:14 <moneromooo> My internet might be off more than on for the next hour or so, good luck
15:44:28 <quila[m]> Cool, thanks for the help.
15:45:10 <quila[m]> Brew didn't install static libs for `libevent`.
15:45:54 <selsta> that's why I thought you might have to compile the dependencies yourself
15:53:32 <quila[m]> <selsta> "that's why I thought you might..." <- I assumed it was good practice to brew recipes include static and shared libs... But `monero/contrib/brew/Brewfile` is definitely missing `nghttp2`.
15:55:33 <quila[m]> I need to come back to this later. Thanks selsta and moneromooo for the help.
16:00:21 <hyc> I didn't catch everything in the scrollback. what's he trying to build on M1?
16:00:58 <selsta> release-static
16:02:21 <hyc> I'll give it a shot. unfortunately the apple version of compilers deviate from gcc/clang normal target names
16:02:48 <hyc> gcc/clang want aarch64-apple, apple compilers want arm64-apple
16:03:16 <hyc> that's one of the things I had to account for in #8312
16:05:26 <selsta> hyc: https://paste.debian.net/1240964/
16:05:32 <selsta> that were the openssl linking errors
16:07:39 <hyc> I just did make release-static and got
16:07:40 <hyc>  24%] Building CXX object contrib/epee/src/CMakeFiles/obj_epee.dir/byte_slice.cpp.o
16:07:40 <hyc> clang: error: the clang compiler does not support '-march=x86-64'
16:07:56 <hyc> something in CMakeLists.txt is still assuming darwin only has x86-64
16:20:44 <selsta> hyc: you have to edit ARCH=x86-64" to default in Makefile
16:21:10 <selsta> make release-static has the ARCH still hardcoded
16:24:27 <hyc> ah I see. I changed it to native for now
16:26:48 <selsta> .merges
16:26:48 -xmr-pr- 8046 8312
16:29:39 <selsta> .merge+ 8315 8308 8307 8266
16:29:39 <xmr-pr> Added
16:30:12 <selsta> jberman[m]: did you run unit tests with https://github.com/monero-project/monero/pull/8330 ?
16:30:24 <selsta> CI has timed out, seems it got stuck somewhere
16:31:36 <selsta> hyc: something else, jeffro256[m] implemented your comment suggestions, can you take another look? https://github.com/monero-project/monero/pull/8322
16:34:47 <hyc> ok
16:35:53 <hyc> I kinda don't see the need for reorganizing sha256 into its own source & header files
16:36:18 <hyc> that strikes me as gratuitous churn
16:36:28 <hyc> anyone else have opinions there?
16:44:44 <hyc> so I just ran into that nghttp2 symbols unresolved etc
16:46:44 <moneromooo> A lot of those epee patches seem pointless, but since I don't contribute much anymore, I'm mostly keeping my mouth shut about it.
16:47:34 <hyc> it's still basic principle of collaborative dev: minimize churn. do the least amount of changes needed to solve the problem, and nothing more
16:47:59 <hyc> unless you decide up front that you're going to tackle a major refactoring
16:48:09 <hyc> which afaik nobody here is trying to do
16:49:11 <ooo123ooo1234[m]> hyc: refactoring just for the refactoring is bad aim too
16:49:17 <ooo123ooo1234[m]> it leads to a lot of redundancy
16:49:40 <hyc> this 8322 touches 14 files just to update the sha256 function
16:49:44 <hyc> that's nuts.
16:56:56 <ooo123ooo1234[m]> <moneromooo> "A lot of those epee patches seem..." <- like instead of fixing some problems inside, someone decide to polish front door
16:56:57 <ooo123ooo1234[m]> hahahaha
16:59:06 <UkoeHB> A nice front door invites people to look inside. Pretty simple concept tbh
16:59:37 <hyc> so libunbound requires -lnghttp2 and -levent
17:00:18 <hyc> ^ as inviting as a venus flytrap :P
17:01:11 <UkoeHB> hey at least they are trapped fixing bugs, instead of running away (which a lot of people do when they see uninviting code)
17:08:26 <moneromooo> Well, since rewriting stuff to the format you like can involve unwittingly adding bugs... it's a neverending churnfest :)
17:09:13 <moneromooo> I suppose differentiating between "I like this better" and "this is really bad code" can be a fuzzy line.
17:10:10 <moneromooo> There was a recent patch for example, where some atomicity was mistakenly lost, and the patch's purpose was to have better atomicity.
17:11:17 <moneromooo> (though the underlying intent was actually right, using std::atomic so you would not forget to call atomic read/write)
17:12:06 <moneromooo> IIRC there were hangers on in the patch too, the "I like it better that way" type. Shrug.
17:12:20 <UkoeHB> Well, surely there is some balance between code quality improvements and in-place changes. In-place changes lead to accumulated technical debt, which makes it harder to find bugs and easier to create bugs with future changes.
17:12:41 <UkoeHB> And also harder to evaluate if new changes are buggy or not.
17:12:46 <moneromooo> Right. And different people put the line in different places :)
17:13:23 <moneromooo> I'm at one extreme, I'll readily admit.
17:14:30 <moneromooo> But hey, I was young too. I once reformatted stuff to remove stray tabs in a code base. That's when I really learnt about conflicts ^_^
17:14:51 <moneromooo> I mean, *really* learnt.
17:15:22 <moneromooo> Like, learnt that they do not come up once and then never again. Unless you never use your VCS's history.
17:15:34 * moneromooo shuts up before going too hard on another rant
17:15:48 <ooo123ooo1234[m]> UkoeHB: I don't believe in any kind of code quality. It always about reading code until you understand what is going on and then something can be changed.
17:16:18 <ooo123ooo1234[m]> How many comments / code quality patches are needed to make code verification / audit easier ?
17:16:35 <moneromooo> If you can afford to spend shitloads of time on code, I'd agree. I don't agree in practice though.
17:17:04 <ooo123ooo1234[m]> Final code verification implies that everything is untrusted and should not be verified outside of context.
17:17:10 <UkoeHB> ooo123ooo1234[m]: yeah, but why the hell would some want to read code if it looks like shit? Even if the reader is qualified and competent.
17:17:31 <jeffro256[m]> Hey yall, sorry I'm late
17:17:50 <jeffro256[m]> I saw that yall were reviewing the SHA256 PR
17:18:28 <UkoeHB> It's just an enormous waste of time to translate shit code into comprehensible logic.
17:19:46 <UkoeHB> I want to spend all my time thinking about the logic, not tracing out some bs execution flow.
17:19:48 <jeffro256[m]> We would have to rewite that SHA256 code anyways because OpenSSL 3.0 doesnt support it anymore but I figured it it was going to be overhauled anyways, might as well make it look clean
17:20:21 <hyc> I don't see how the particular source file its in affects its cleanness or code quality
17:20:36 <moneromooo> What do we use SHA256 for btw ? I know of the update check, anything else ?
17:21:18 <jeffro256[m]> Because we have a giant 2K+ file called "util.cpp" that is largely undertested and unorganized 
17:21:20 <moneromooo> If it is just that, we can just use keccak instead, since it doesn't have to be compatible with anything else.
17:21:49 <ooo123ooo1234[m]> UkoeHB: any short example ?
17:21:56 <jeffro256[m]>  Sorry 1.4K 
17:22:51 <moneromooo> Hmm. Merge mining (can be changed, not too late), trezor (probably hard to change).
17:23:27 <jeffro256[m]> It's used also in merge mining I believe
17:25:03 <kayabanerve[m]> ... does anything actively merge mine with Monero right now?
17:25:07 <kayabanerve[m]> ... I'd guess Wownero?
17:25:15 <kayabanerve[m]> * guess Wownero if I had to pick a project to do so?
17:25:20 <UkoeHB> ooo123ooo1234[m]: https://github.com/monero-project/monero/blob/8349cfe4a63cfc63d50ce3818886b67a05e240a4/src/wallet/wallet2.cpp#L13504 . Figuring out if `update_multisig_rescan_info()` introduced a nonce-reuse bug was a waste of time that could have been avoided with a better design (i.e. code quality).
17:25:35 <moneromooo> I was going to say nothing. I didn't knopw about wownoero.
17:25:47 <moneromooo> That is interesting.
17:26:02 <kayabanerve[m]> Yeah, me neither
17:26:07 <selsta> as far as I know they don't merge mine
17:26:24 <kayabanerve[m]> IMO, Monero shouldn't have any merge mining code. At all. If another project wanted to setup some merge mining system, that should be completely on them.
17:26:29 <jeffro256[m]> Does townforge merge mine with Monero is it a seperate chain?
17:26:35 <moneromooo> Tari was the one who wanted to merge mine. Townforge also will. 
17:27:03 <kayabanerve[m]> And I don't care to submit a PR removing the TX Extra byte, as it increases extra decode rate to have it, but if we're saying merge mining somehow has compatibility requirements...
17:27:20 <moneromooo> Merging that code means any project can reuse it, which means more hash rate going into monero.
17:28:10 <moneromooo> In theory anyway.
17:28:53 <kayabanerve[m]> Isn't the code in question simply a cleanup of the sha function solely used for updating? How does this feed into merge mining anyways?
17:29:57 <moneromooo> MM just uses sha256 because it was there and I needed a hash function I think. Not sure why I picked this one and not keccak.
17:30:13 <jeffro256[m]> I would have to look deeper into it, but I believe that that the merge mining code uses it it validate the intgerity of the merge mined blockchsind
17:30:22 <moneromooo> (hence "can be changed, not too late").
17:30:46 <kayabanerve[m]> Tari is already proposing proxying the Monero mining RPC for its needs.
17:31:47 <kayabanerve[m]> Considering nothing actively uses this, it personally sounds like MM should be moved to keccak256 at least, or we should drop code from it and leave Tari to augment their proxy to replace the dropped code.
17:34:49 <kayabanerve[m]> Just to be perfectly clear, the MM code in Monero. It's solely indexing data and providing RPC methods, right? None of it actually affects node operations?
17:35:06 <moneromooo> Right.
17:35:09 <moneromooo> IIRC.
17:35:13 <moneromooo> It's been a while now...
17:35:34 <jeffro256[m]> sha256 is also used to verify the checkpoints.dat file , but that could easily be changed 
17:35:38 <moneromooo> It was meant as an incentive to other chains to start using MM.
17:35:59 <moneromooo> But nobody seemed to care so far.
17:36:24 <moneromooo> Probably too busy doing stuff for that ethereum house of cards before it crashes down under its own weight :D
17:36:53 <ArticMine[m]> I can see this changing with tail emission
17:37:52 <ArticMine[m]> MM with Monero could be seen as an option
17:41:38 <jeffro256[m]> Does anyone know the comparison of cryptographic security between keccak and SHA256? Because we only "need" one good cryptographicly secure hash function
17:42:06 <hyc> keccak is the basis for SHA3
17:42:24 <hyc> I would say it's superior to all SHA2 algos in every meaningful way
17:43:20 <kayabanerve[m]> I still prefer Blake2b :( But that's a derailment for another day :p
17:44:01 <moneromooo> Was this a SHA3 candidate ?
17:44:08 <kayabanerve[m]> But yeah, keccak is effectively SHA3. It's just minor padding changes from the submitted contestant to the released version that causes people to still call it keccak.
17:44:22 <jeffro256[m]> @hyc that's what I figured since it was a SHA3 finalist , so maybe we could start to transition away from SHA256?
17:44:40 <kayabanerve[m]> Blake2 and Keccak were both candidates. Keccak had lower performance but was more distinct and provided redundancy in case SHA2 was broken IIRC.
17:45:09 <hyc> blake2 was also designed specifically to be fast on CPUs
17:45:13 <kayabanerve[m]> Keccak was chosen and just had the padding changes I don't think affect its security in any meaningful way.
17:45:27 <kayabanerve[m]> We should drop SHA2 though
17:46:29 <moneromooo> So... if openssl drops SHA256, does it mean it doesn't support any suite that uses SHA256 ? Or did it just drop it from its public API ?
17:46:53 <jeffro256[m]> Just the suite of APIs we were using
17:47:08 <jeffro256[m]> You can still use it thru the EVP API
17:47:27 <hyc> they totally revamped their hashmech API
17:50:44 <ooo123ooo1234[m]> <UkoeHB> "ooo123ooo1234: https://github...." <- A better design already known to a reader. Untrusted code verification will be always as hard as this (https://en.wikipedia.org/wiki/Boolean_satisfiability_problem). Even if this state is reached at some point, with addition of anything new full verification will be needed again. The only way is to maintain knowledge about code in memory. Only code of dead project is easy to review.
17:50:44 <ooo123ooo1234[m]> hehe
17:52:41 <hyc> quila[m]: this makes the static build succeed on M1 Mac
17:52:46 <hyc> https://github.com/monero-project/monero/issues/8332
17:56:32 <UkoeHB> ooo123ooo1234[m]: how about a design where copies of nonces are never made, so even the question itself doesn't have to exist?
17:56:58 <sech1> sha3 uses exactly the same keccakf1600 function in the main loop, the only difference is the initial message padding
18:01:29 <UkoeHB> ooo123ooo1234[m]: plus, my complaint was about TIME, converting code into a comprehensible mental model takes time, and it takes less time if the code is cleanly written. Saying you don't want to write clean code is like saying you want to waste people's time (when clearly you are obsessed with other people wasting your time, quite the double standard).
18:03:17 <moneromooo> I think this is an issue of "bandwidth". The code "cleverness" has to be high enough that it's good and able, but low enough than enough people can work with it. Too clever and only very few people can handle it, and it'll end up untrusted because few people can verify it. Too low and it's full of gunk.
18:03:26 <moneromooo> You want a sweet spot.
18:03:58 <moneromooo> And of course I've been advocating for keeping some of the gunk because churn in itself adds some gunk despite the apparent gunk removal...
18:05:12 <moneromooo> Bandwidth should not be a bottleneck. You really want to avoid bottlenecks, of which there are many.
18:05:52 <moneromooo> "Bandwidth" is probably not the best term here. For the purposes of this argument, I define it as "number of people times their ability to go through and grok the code".
18:06:27 <moneromooo> Another bottleneck is the number of independent people being able to read and understand the code. Or at least parts of the code, realistically.
18:06:41 <moneromooo> It's a balancing act, sadly. No magic bullet.
18:10:51 <UkoeHB> There are so many simple things you can do to speed up reading code. Good naming, functions that do only one thing, small comments that help you orient yourself when re-reading code, whitespace that helps the reader parse language syntax. And advanced stuff like minimizing raw loops and conditionals, very judicious use of inheritance, strict interfaces and well-understood pre/post conditions, etc.
18:14:01 <ooo123ooo1234[m]> UkoeHB: Do you know any code that meets all of this but is vulnerable ?
18:15:07 <UkoeHB> ooo123ooo1234[m]: Where did I saw clean code is invulnerable? I said clean code is easier to read. Maybe you should re-read my reading rant.
18:16:10 <moneromooo> It was not claimed you said that. It's just about shifting a probability distribution.
18:16:18 <ooo123ooo1234[m]> UkoeHB: Does "easier to read" mean easier to verify correctness ?
18:16:49 <sech1> Any code more complex then "hello world" has bugs/vulnerabiliteis, it's inevitable. The scale and severity of these bugs can be restricted by good coding/testing/reviewing practices.
18:16:50 <moneromooo> Easier to understand means easier to verify correctness.
18:16:52 <UkoeHB> It means easier to find people willing to verify correctness, and less cost for anyone who wants to verify correctness.
18:17:19 <UkoeHB> because time = money
18:18:07 <moneromooo> But "verify correctness" for large enough code is practically impossible since the combinatorics are just too large. It's *really* hard to keep a large state in one's mind, especially when it changes and rolls back.
18:18:18 <ooo123ooo1234[m]> UkoeHB: There must be at least 1 example of code that was written in accordance with all of that subjective standards, audited but turned out to be vulnerable
18:18:32 <moneromooo> And that's what's needed to *verify* correctness.
18:18:33 <ooo123ooo1234[m]> or redundancy added by clean code standards helped to hide vulnerability
18:19:26 <moneromooo> ooo123ooo1234[m]: you could ask, eg, trail or bits or similar for a bit of code where they found a vuln and the code was really clear/nice/etc.
18:19:35 <moneromooo> s/ or / of /
18:20:03 <sech1> ooo123ooo1234[m] just read articles at https://pvs-studio.com/en/blog/posts/cpp/ - plenty of examples
18:20:04 <moneromooo> People like that would likely remember such cases, as htey're their biggest successes.
18:20:56 <sech1> on topic of clean code with vulns: https://pvs-studio.com/en/blog/posts/cpp/0935/
18:23:27 <UkoeHB> ooo123ooo1234[m]: surely there are many such examples. Are you going to ask for a statistical comparison between vulnerable shit code and vulnerable clean code? Maybe I should ask YOU for that statistic, since it's pretty easy to assume that shit code is more likely to contain bugs (i.e. not just conceptual errors, but literal software bugs that can be exploited).
18:25:55 <sech1> For me, "clean code" is also code that doesn't trigger compiler warnings at highest warning level and is regularly checked by static analyzers. It helps to catch 90% of coding errors.
18:27:23 <sech1> then come automatic unit tests and integration tests that catch 9% more bugs. 1% is left which are really tricky logic errors or thread races etc. - but no simple bugs.
18:28:06 <sech1> also AddressSanitizer, ThreadSanitizer and UB Sanitizer are really helpful
18:28:27 <moneromooo> As long as -Werror is not used. What a shit idea that one was...
18:28:55 <sech1> -Werror works fine in p2pool. But I had a luxury to keep in like that from the start.
18:29:00 <sech1> *keep it
18:31:41 <hyc> there's a lot of subjectivity about what is readable and comprehensible
18:32:10 <moneromooo> Hence the "please don't rewrite to how you like it better".
18:32:19 <hyc> if you want to understand why something was done the way it was, the code itself may not be obvious
18:32:37 <hyc> and so you may have to trawl thru the commit history to understand the evolution of the code and why
18:32:57 <hyc> so what is *objective* is the fewer changes you make to the code, the easier the history is to grok
18:33:12 <ooo123ooo1234[m]> hyc: don't know any example where code itself isn't obvious
18:33:24 <ooo123ooo1234[m]> * itself isn't <del>obvious, * obvious</del> enough
18:33:30 <hyc> these are pretty well established principles in colalborative software development
18:33:34 <ooo123ooo1234[m]> I find it harder to read other people text than code
18:33:54 <moneromooo> Did you every look at the IOCCC ? Some of that stuff is really clever.
18:34:33 <hyc> ooo123ooo1234[m]: e.g. n wallet code there are some warnings for unused vars. why do they exist? were they put in for a yet-to-be-implemented feature?
18:34:43 <hyc> or left over from a previous code removal "cleanup" ?
18:34:49 <hyc> only the commit history can explain
18:35:18 <UkoeHB> hyc: sure, there is subjectivity. There are also very obvious things that few people can disagree with. For example, you don't write a book with font size 3 if you want people to read it.
18:35:31 <moneromooo> Oh, that one's mine IIRC. There was something I needed to get back to, and removing the warning would just lose the reminder. Never did :/
18:35:33 <hyc> #1 rule in a project must be "change only what is necessary and nothing more"
18:35:49 <wernervasquez[m]> ooo123ooo1234[m]: Isnt enough for what?
18:35:52 <moneromooo> And tbh I doubt I'll get to it. If someone else wants to fix it...
18:36:37 <moneromooo> ooo123ooo1234[m]: did you mean "I find it harder to read other peopls's written language than other people's code" ?
18:36:50 <hyc> e.g., these are the guidelines we've used in OpenLDAP https://openldap.org/devel/programming.html
18:37:28 <moneromooo> (and yes, it's a good example of that, heh)
18:38:40 <selsta> https://github.com/monero-project/monero/pull/6310
18:38:43 <selsta> this one I think
18:39:05 <UkoeHB> ooo123ooo1234[m]: so what, everyone should be like you (a C++ compiler or something?)? is that a realistic way to get anything done?
18:39:36 <moneromooo> Yes. That one would just sweep something under the carpet. Very good example of mindless kowtowing to compiler.
18:40:38 <moneromooo> ooo123ooo1234[m]: I am going to assume you are a competent coder who would like to make monero better here.
18:40:42 <hyc> another rule of open source development is you never get to dictate the style of a project you join in-progress. you always adopt the existing coding style.
18:41:15 <moneromooo> This is in a way similar at a high level to free software. There are constraints in the licence, so how can it be free ?
18:42:07 <moneromooo> The point is that the freedom is that of the software, not of any particular user. And of users as a whole over any particular user. Though this is subject to interpretation and I'm not sure this is the right way of saying this, but anyway:
18:43:25 <wernervasquez[m]> hyc: Or, depending on the license, fork it. Put in the work. And let the merits of your ideas speak for themselves. 
18:43:37 <moneromooo> This is my take on it, not the definite trust of course: In order to build a piece of software, I think you want the highest "bandwidth" of work on it. That bandwidth improves with the numer of people working on it, and also with the competency of people working on it.
18:44:02 <hyc> wernervasquez[m]: sure, that's always an option
18:44:08 <moneromooo> However, different people have different abilities. You can't improve everyone's competency.
18:44:24 <hyc> if you want to contrinbute a patch to the linux kernel, you must code to the linux kernel coding style.
18:44:37 <hyc> you can fork the kernel and reformat if you really want to, but that would be stupid
18:44:50 <moneromooo> If people work on the same codebase, they have to settle down at roughly the lowest common denominator of competency, or the people who don't understnad the code will drop off.
18:45:22 <moneromooo> So you either have to drop "cleverness" to include more people, or increase cleverness to drop them off and make up numbers for "good code".
18:46:10 <moneromooo> This can to some extent be solved by having people work on only part of the code. Like, say, clever cookies work only on clever crypto, where people like me won't have to understand it.
18:46:43 <moneromooo> Why the fuck am I doing explaining what's obvious. It's patronizing. I'll shut up.
18:46:59 <hyc> I thought you were doing fine.
18:47:09 <hyc> it seems a lot of newer contributors don't understand
18:47:22 <moneromooo> But I know for a fact it's hard to  dumb down your code. Some people I find useless, and it's difficult to constantly try to explain things agian and again.
18:48:03 <moneromooo> But you need to do that or end up essentially on your own and you'll achieve... not much.
18:48:34 <moneromooo> If you're after self development, it'll work fine. If you're after building something great others can help you with, you'll crash and burn.
18:49:43 <moneromooo> And I'm here in the middle I think. I see shit people around, and people like sarang who are able to grok all the crpto and still write the C++ to go with it. So I think I see both sides.
18:50:29 <moneromooo> So if you want the project to grow, and not just you, you need to allow others - up to a point. IT's not a kindergarten project.
18:51:20 <moneromooo> And yes, that means others will just be blind to obvious stuff. Apologies to everyone who thought I was a dunce for asking obivous stuff avout crypto repeatedly.
18:51:53 <jeffro256[m]> Yeah that's pretty well put 
18:52:06 <moneromooo> But if you try and let others be able to grok your stuff, it'll grow the project faster than you could have done alone.
18:52:24 <moneromooo> Especially once you decide to fuck off :D
18:53:11 <jeffro256[m]> If you look at the biggest, most popular libraries and codebases, thing that are actually used by millions on a daily basis, it's not the code that it the cleverest, it's the stuff that has the the most numbskulled, dead-easy API to use
18:53:53 <moneromooo> I'm feeling conflicted saying that and writing some code that's not the easiest to read though :D
18:53:59 <moneromooo> (sorry guys)
18:54:17 <hyc> that's reality. some things are just hard.
18:54:40 <moneromooo> Anyway. That explains why sometimes it's just best to kick someone in the butt out of here if they persist in being assholes.
18:54:59 <hyc> if it's too hard to understand and you don't want to put the effort in, fine, nobody's forcing you. move on to some other project if you want.
18:55:01 <moneromooo> Just not worth the bother. Try not to be that guy,
18:55:05 <jeffro256[m]> That's okay honestly, but I think what has been missing so far is someone to come clean it up for the rest of us plebians
18:56:04 <wernervasquez[m]> hyc: There is a tradeoff at somepoint though. Unless you goal is to work alone.
18:56:48 <hyc> the goal is to solve problems. some problems are just hard by their nature.
18:57:01 <moneromooo> Well, it's always a balancing act, isn't it... Sometimes shepherding newbies is just more trouble than you get back.
18:57:08 <jeffro256[m]> I probably won't be able to contribute to critical code for a long, long time, I'm just not that confident in my abilities yet, but what I think is currently missing is like a two prong approach that a lot of companies take on where you have some people write the code and others that make it easier to grok
18:57:49 <hyc> seriously. if this were easy everyone would be doing it...
18:57:49 <moneromooo> That seems... dangerous...
18:58:20 <ooo123ooo1234[m]> jeffro256[m]: are you talking about regular for-profit companies ?
18:58:23 <hyc> ^ yeah, shades of the debion openssl RNG bug
18:58:37 <moneromooo> Heh. Exactly.
18:58:59 * moneromooo wonders if that was patronizing or helpful...
18:59:42 <UkoeHB> There are risky changes, and there are not risky changes. Moving functions out of a bloated file is not risky.
18:59:49 <hyc> open source s/w dev is not like commercial s/w dev. there are no assigned roles
19:00:03 <moneromooo> Maybe not risky, but conflicty as hell.
19:00:12 <jeffro256[m]> @ooo123ooo1234 yeah
19:01:26 <jeffro256[m]> @hyc yeah there are no "assigned" roles but some people tend to focus on some things, and that's alright you gotta play to each other's strengths and we can use each other to patch each other's weaknesses
19:01:41 <jeffro256[m]> No one has to write perfect code the first time 
19:01:42 <hyc> "bloated file" is also subjective. if you only need to look inside that file once every 10 years because some upstream dependency changed their API, it's hardly a problem worth spending time on
19:02:40 <UkoeHB> maybe you don't need to look in that file, but any newcomer learning the codebase probably needs to look in it
19:03:12 <moneromooo> The issue with size is compile time. If you read code, where hte code is is mostly irrelevant, no ?
19:03:40 <UkoeHB> large files are incredibly hard to navigate
19:03:48 <hyc> If someone needs to read the source of util.cpp on a regular basis, something is terribly wrong.
19:03:52 <UkoeHB> the only way I can get around wallet2 is ctrl-f for things I already know about
19:03:53 <moneromooo> Like, I created wallet2_cc.cpp for new stuff in my fork, but that's just for memory usage.
19:04:00 <hyc> they should only need to read util.h to make use of its functions
19:04:46 <moneromooo> Would you... not search for stuff if the file was, say, 500 lines ?
19:04:54 <hyc> that's like saying someone needs to read the source of malloc() on a regular basis
19:05:19 <moneromooo> Reading malloc as an exercise in working out why something that should be simple is fucking complicated :D
19:05:26 <moneromooo> Or... printf...
19:06:12 <hyc> it's a utility, you just use it and move on...
19:06:37 <UkoeHB> moneromooo: it's not about the usefuless of searching, it's that searching is the ONLY way to navigate
19:06:52 <hyc> there is such a thing as ctags
19:06:57 <UkoeHB> and if you don't know what you're looking for, it's doomed
19:07:25 <moneromooo> OK. I guess we just have different ways to work. I always git grep and / search.
19:07:28 <jeffro256[m]> @hyc I tend to agree with UkoeHB here, you are a wizard and have spent a lot of time in the code. But for the rest of us, we can't see it as "just a utility:" because we don't know what ir does and its mostly undocumented and unorganized
19:07:39 <moneromooo> So file size is irrelevant for me.
19:07:46 <ooo123ooo1234[m]> moneromooo: the same
19:07:47 <wernervasquez[m]> hyc: I know how you feel dero (scam). And I am not promoting or defending it as a project. But speaking solely about the code base, have you ever read their re-implementation of monero's stuff in Go? I think it is objectively better code.
19:08:03 <jeffro256[m]> It just creates a lot of mental friction for someone trying to understand the codebase at large 
19:08:22 <hyc> jeffro256[m]: that's just the wrong approach
19:08:30 <hyc> you can't understand the codebase at large.
19:08:33 <sech1> "better code" is a subjective category unless we define some metrics
19:08:37 <hyc> you find one piece and work from there
19:09:09 <hyc> and in any piece of code - the header file is the interface. if you need to look beyond that, there's something wrong
19:09:13 <sech1> "one piece" <- assuming the codebase is nicely split into independent pieces and not just one huge cpp file :P
19:09:14 <hyc> with the interface
19:09:35 <UkoeHB> moneromooo: for me, knowing the relative location of every function and piece of logic makes it easier to get things done
19:09:51 <hyc> util.h is 259 lines, at least 30% comments
19:10:17 <hyc> so it seems like not a big deal to grok, as someone who wants to use it
19:10:18 <sech1> For me, file size is not a big ussue as well. I've seen huuuuge files in commercial codebases I worked on (I'm talking about > 50,000 lines)
19:10:28 <moneromooo> OK. I have trouble understanding why it helps, but I acknowledge it does.
19:10:38 <UkoeHB> I almost never read monero's headers, always look at the source functions to figure out what they are doing first.
19:11:05 <jeffro256[m]> hyc All but one utility function in util.h has not a single comment
19:11:35 <hyc> jeffro256[m]: you're exaggerating, quite a bit
19:11:35 <jeffro256[m]> Ah well theres a few at the top actually but that still leaves 16 undocument functions
19:11:58 <UkoeHB> I basically default to looking at source for most things (some of the ringct.h and crypto.h stuff is usable).
19:12:01 <jeffro256[m]> Sorry I saw the ones between the class declarations but still
19:12:54 <hyc> bool disable_core_dumps();  - you should be able to tell from the signature whether it's a function you care about or not
19:13:23 <moneromooo> I should have called it discd so I could have added a comment.
19:13:29 <wernervasquez[m]> The purpose of the project matters. If you are trying to write the most efficient miner or database, nobody really cares if the code is readable by a junior dev. They just was speed and correctness.
19:13:30 <hyc> LOL
19:23:42 <ooo123ooo1234[m]> <wernervasquez[m]> "The purpose of the project..." <- it's unreachable goal - different people have different experience / abilities / ...; What's the goal to tune code readability for someone who don't know it if such people can't even verify correctness of their changes ?
19:25:51 <ooo123ooo1234[m]> <UkoeHB> "I almost never read monero's..." <- code is the most detailed source of info, what kind of detalization is ok for function header ? different cases require different detalization
19:26:08 <ooo123ooo1234[m]> in the worst case function header should comment with it's source above
19:26:14 <ooo123ooo1234[m]> hence it's the most detailed comment
19:26:19 <ooo123ooo1234[m]> I did it few times at work 
19:26:20 <ooo123ooo1234[m]> hehe
19:26:38 <ooo123ooo1234[m]> * header should have a comment with
19:26:54 <hyc> C++ particularly sucks because so much of implementations are in headers anyway
19:27:06 <hyc> you wind up needing to read header and source for anything you're trying to debug
19:27:56 <UkoeHB> ooo123ooo1234[m]: the point was about navigating large code files and using stuff from them. It’s not as simple as looking in the header.
19:30:05 <ooo123ooo1234[m]> UkoeHB: What did you use for source file navigation last time ? vim / some IDE ? Do you use advanced navigation features ? Does it help ?
19:30:26 <UkoeHB> ooo123ooo1234[m]: the purpose of Monero is a private cryptocurrency that any person can use. How is writing code that any person can read for their own satisfaction, for the cryptocurrency they use, not also a good goal?
19:31:37 <UkoeHB> ooo123ooo1234[m]: I mainly use the find-all feature in sublime text which works pretty good (I suck at remembering shortcuts, so vim won’t work for me).
19:33:01 <UkoeHB> But I don’t use that for stuff whose location I already know.
19:35:24 <UkoeHB> Location is just an easier way to navigate for me (and conceptualize) than named lookups.
19:36:45 <UkoeHB> There is no ‘what’s that big generic file that has what I want? what’s the exact name to find it?’
19:37:51 <jeffro256[m]> ooo123ooo1234 why not put all of src/common into one header file and make all the functions inline? That would make it easier to CTRL-F it
19:55:35 <jeffro256[m]> @hyc @selsta UkoeHB I pushed to the Sha256 PR btw with a smaller test file and I wrap EVP_MD_CTX in a class so it never leaks
20:46:15 <quila[m]> <hyc> "https://github.com/monero-..." <- Thanks for the help. I have tested this and got less errors now:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/cd9f94da0e830f877f7d93699b1451bfa6460b0d)
20:46:31 <jeffro256[m]> Also btw the evp.h file is not going to be a one-off file for sha256sum. There's other parts of the codebase that are deprecated by OpenSSL 3.0 but which the EVP-equivalent isnt 
20:47:28 <jeffro256[m]> > > <@hyc:libera.chat> https://github.com/monero-project/monero/issues/8332... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/fa0c4e0ecef164e1fa28557c4dc9f5cbe0b8b554)
20:51:19 <hyc> quila[m]: strange, I didn't get those errors. those symbols are from openssl
21:00:06 <hyc> that's a system library on macos. On mine it's actually libressl 2.8
21:05:00 <hyc> hm. no I've got homebrew openssl 1.1.1l in /usr/local/lib
21:07:57 <ooo123ooo1234[m]> hyc: There are too many environments to support all of them by default. It's enough to maintain at most one cross platform environment for all targets.
21:08:15 <ooo123ooo1234[m]> It's just waste of time to figure out what decomposition of headers/libs is being used by some env
21:11:27 <hyc> dunno which conv you're responding to
21:11:57 <hyc> but yes, that's why we use gitian for official reproducible binaries. single env for all targets.
21:17:38 <ooo123ooo1234[m]> hyc, "It's easier to make a correct program run fast than to make a quick program run correctly!" 
21:17:47 <ooo123ooo1234[m]> cool thesis
21:17:56 <ooo123ooo1234[m]> "https://openldap.org/devel/programming.html" from here
21:22:14 <hyc> yes
21:22:35 <hyc> we've lived with that philosophy for ~24 years on the project
21:23:25 <hyc> and also happen to perfectly conformant with protocol specs and world's most efficient implementation
21:23:43 <hyc> correctness comes first.
21:32:47 <quila[m]> <hyc> "hm. no I've got homebrew openssl..." <- I have set the FLAGS to use openssl 1.1, but got a problem with boost lib now.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/eeba14e14f68121c2c9042381aae822b3392150c)
21:33:39 <quila[m]> icu to be more precise.
21:34:33 <garth> Testnet fork is tomorrow. If I want to help debug the switch I should git pull from master today?
21:36:09 <quila[m]> hyc: how can I set multiple `CPPFLAGS`? Would something like `export CPPFLAGS="-I/opt/homebrew/opt/icu4c/include:$CPPFLAGS" work?
21:42:42 <selsta> garth: yes
21:57:54 <hyc> quila[m]: why do you want to change CPPFLAGS? that won't make any difference here
21:58:15 <hyc> strange that my homebrew libboost doesn't have this problem
22:01:35 <hyc> quila[m]: at this point it seems like more trouble than it's worth
22:01:48 <hyc> the gitian build for M1 Mac in #8312 works
22:02:24 <hyc> I have no idea what's different about your homebrew install that's breaking these library dependencies
22:03:03 <hyc> not worth my time to help you figure that out when I've already created a reproducible build environment for M1 that everyone can use
22:04:32 <quila[m]> No problem. Thanks for the help anyways. I will investigate further tomorrow.