04:10:17 <scoobybejesus> So we're breaking tradition and not re-tagging?  Nice.  :P  Mine appear to be the same:  https://paste.debian.net/1159128/
05:05:26 <luigi1111> first time for everything
05:46:12 -xmr-pr- zhouqiang-cl opened issue #6742: Using Chaos Engineering to enhance monero
05:46:12 -xmr-pr- > https://github.com/monero-project/monero/issues/6742
09:16:12 -xmr-pr- yzn5555 opened issue #6743: xmr节点生成新的地址耗时5分钟
09:16:12 -xmr-pr- > https://github.com/monero-project/monero/issues/6743
09:26:16 <fluffypony> https://github.com/monero-project/monero/issues/6743
09:26:24 <fluffypony> is there anyone that reads and writes Chinese?
09:26:55 <Inge-> @realsexycyborg :P
09:29:01 <Inge-> there is also the monerocn TG group
09:30:18 <fluffypony> lol
10:30:09 <moneromooo> re-tagging ? Did the .3 replace an existing tag ?
10:30:37 <hyc> my hashes also match http://paste.debian.net/1159169/
10:42:52 <iDunk> I don't think it did. There is no .2 in my gitian out dir.
10:45:05 <moneromooo> Good :)
12:16:57 <moneromooo> TheCharl1: are you TheCharlatan ?
12:17:28 <moneromooo> If so, mind commenting on https://github.com/monero-project/monero/pull/6337, the last tweak to which removes an addition you made to fix cross compilation ?
12:17:39 <moneromooo> It apparently breaks something for vtnerd.
13:54:28 <selsta> my hashes also match https://paste.debian.net/hidden/8877b892/
14:00:01 <sethsimmons> I'll kick off my build now
14:00:28 <sethsimmons> I'll stop mining for a bit 🥲
14:09:00 <sethsimmons> I think I had to ask this before and have forgotten the fix -- running into an isssue getting packages for the gitian build: `Unable to connect to 172.17.0.1:3142`
14:09:29 <selsta> wasn’t it firewall related?
14:09:35 <iDunk> IIRC, it was the firewall last time.
14:10:27 <sethsimmons> ah I'll double check
14:11:03 <sethsimmons> yup fixed with `sudo ufw allow 3142/tcp`
14:11:19 <sethsimmons> Forgot I rebuilt fw since the last tagged release
14:11:22 <sethsimmons> Thanks!
14:31:12 -xmr-pr- LordSquigles opened issue #6744: [P2P8]  ERROR   default src/common/threadpool.cpp:118   wait should ha...
14:31:12 -xmr-pr- > https://github.com/monero-project/monero/issues/6744
14:32:05 <moneromooo> https://github.com/monero-project/monero/pull/6745 is the unlock time change I'd like to have for the fork.
14:32:25 <selsta> ok
14:32:36 <selsta> soo CLSAG + this need a review
14:36:05 <selsta> moneromooo: would you also like https://github.com/monero-project/monero/pull/6616 ?
14:39:57 <moneromooo> If it gets reviewed, sure.
14:40:11 <moneromooo> It's not a must have though.
14:46:12 -xmr-pr- moneromooo-monero opened pull request #6745: Use recent block times for unlock time
14:46:12 -xmr-pr- > https://github.com/monero-project/monero/pull/6745
14:46:24 <Snipa> .merges
14:46:24 -xmr-pr- 6418 6500 6536 6538 6542 6546 6565 6571 6593
14:56:52 <Snipa> Looks like the bot's a bit shot.  6536/6538 are both merged already
14:58:07 <Snipa> As is 6565
14:59:48 <dsc_> Snipa: Could you issue a .merges once more?
15:00:02 <Snipa> .merges
15:00:02 -xmr-pr- 6418 6500 6536 6538 6542 6546 6565 6571 6593
15:00:12 <Snipa> I've just merged 6571 and 6418
15:00:13 <dsc_> yep okay, thanks
15:23:26 <sethsimmons> Linux hashes match for gitian builds
15:23:52 <sethsimmons> Do we want a Reddit thread for the hashes/gitian for this tag?
15:24:58 <sethsimmons> I can create it cloning an old one if someone can tell me the main features/fixes in 16.0.3
15:28:37 <moneromooo> DoS fixes.
15:29:36 <sethsimmons> Thanks
15:31:34 <sethsimmons> Is there a specific PR I can link to for that moneromooo
15:31:53 <sethsimmons> https://github.com/monero-project/monero/pull/6554?
15:32:13 <moneromooo> 6728
15:32:51 <sethsimmons> Great, thanks.
15:33:06 <sethsimmons> https://www.reddit.com/r/Monero/comments/i47ggi/cli_v01603_nitrogen_nebula_has_been_tagged_you/
15:33:14 <caralho> 6536
15:35:19 <sethsimmons> Was that a response to me caralho
15:36:19 <caralho> nope, sry. Testing something out
15:37:33 <sethsimmons> ah ok, thanks :)
15:39:17 <dsc_> xmr-pr got rate limited by github, the bot will return later today
15:39:38 <dsc_> I've put him in the naughty corner.
15:56:46 <sethsimmons> Android/FreeBSD also match so far
17:19:45 <sethsimmons> Ran into an error building windows: https://paste.centos.org/view/1a15e3e7
17:20:51 <iDunk> Looks like OOM killer.
17:21:34 <scoobybejesus> How many cores and how much memory?
17:21:51 <binaryFate> Could anyone who wants to confirm the hashes for v0.16.0.3 CLI please commit to the gitian repo?
17:21:56 <iDunk> I build with -j5 and m12000.
17:22:08 <sethsimmons> 16c/32t
17:22:11 <sethsimmons> Did -j32
17:22:19 <iDunk> lol
17:22:26 <sethsimmons> Should I change to -j16?
17:22:33 <asymptotically> sethsimmons: how much ram have you got?
17:22:43 <sethsimmons> 32G
17:22:55 <sethsimmons> But Monerod and a few other things are running and eating some RAM
17:23:15 <asymptotically> -j24 works for me with 32g
17:23:36 <sethsimmons> I'll try with that
17:23:50 <sethsimmons> I've built fine with -j32 in the past
17:23:52 <sethsimmons> But might be hitting a cap slightly now
17:23:57 <asymptotically> i think that the problem is just with linking. the llvm cmake scripts let you limit the max number of link jobs running at once. not sure how it works but maybe we can steal it? :D
17:24:17 <asymptotically> or tell make that some of the bigger files need to be run alone
17:25:02 <sethsimmons> No idea how to change those
17:26:15 <sethsimmons> Restarting all builds with -j16 instead
17:26:18 <sethsimmons> wish me luck
17:26:44 <iDunk> You don't have to build everything from the start.
17:27:09 <iDunk> Just add -owm if Win and Mac builds are the only ones left.
17:27:12 <sethsimmons> How do I skip certain builds/only run Windows?
17:29:57 <sethsimmons> Comment out other platforms from gitian-build.py?
17:30:14 <iDunk> No
17:30:36 <iDunk> Insert -ow in your command if you only want to build for Windows.
17:30:48 <sethsimmons> -owm for windows and mac?
17:30:51 <sethsimmons> Mac had yet to run
17:30:58 <iDunk> Yes
17:32:01 <sethsimmons> nice that worked, thanks
17:33:49 <sethsimmons> any recommendations for the `--memory` flag?
17:33:58 <sethsimmons> Set it to 12000 at some point but could probably be refined
17:35:25 <sethsimmons> ThreadRipper 1950X 16c/32t w/ 32GB RAM
17:36:07 <iDunk> Use as much as you can spare, I guess.
17:36:28 <iDunk> I use -m12000 as I can spare ~12GB out of 16 GB on that machine.
17:36:50 <sethsimmons> sweet, thanks.
18:07:17 <hyc> I never specify the memory flag
18:07:23 <hyc> just lt it use as much as there is
18:11:46 <hyc> of course, my laptop has 32GB RAM and 8 cores. 4GB per build thread is enough, so far
18:12:05 <hyc> we really need to reign in all this header file madness
18:12:56 <moneromooo> Someone did show up a couple months ago promising large gains in that area.
18:13:00 <hyc> all those templates in the epee networking code are just totally unnecessary
18:13:07 <moneromooo> There was a CCS for it.
18:13:16 <hyc> yeah, I remember seeing that
18:13:30 <moneromooo> I suspect it was overeager promises but decided to waut and see :)
18:13:44 <hyc> frankly it galls me to see people come in out of nowhere and demand money before they pitch in and help
18:14:08 <hyc> they should just stick to working for commercial software companies if that's their attitude
18:14:25 <selsta> they did some contributions FWIW
18:14:32 <selsta> ccache stuff
18:14:55 <moneromooo> That's a weird one. I've been using ccache for years without any change.
18:15:24 <hyc> I don't see anywhere ccache can help in this project
18:15:37 <moneromooo> My sanity.
18:15:46 <hyc> if you touch a header file and force a recompile, that's unavoidable
18:15:59 <hyc> if you don't touch any header files, make already does the minimal required work
18:16:10 <moneromooo> It still helps a lot. Changing defines for example. ccache also caches preprocessed source.
18:16:19 <hyc> ccache is just superfluous. even more ludicrous, it's part of the gitian builds
18:16:20 <moneromooo> And when you rebase and change branches. Oh boy does it help.
18:16:29 <hyc> even though gitian spins up a fresh docker image for every build
18:16:37 <caralho> thats hyperbole
18:16:38 <hyc> there is nothing cacheable/reusable
18:16:39 <moneromooo> It's definitely not superfluous. I love ccache ^_^
18:16:57 <hyc> for gitian, it's useless. completely.
18:17:11 <moneromooo> Well, if is in a fresh fs, sure. But that doens't mean it's superfluous. Just superflous in this partiuclar case.
18:17:37 <moneromooo> But it's mostly irrelevant since it can be used without anything changing in monero anyway.
18:18:12 <moneromooo> If I didn't have ccache, I'd probably have loads of "fixup this shit" commits :/
18:18:22 <hyc> that would improve the codebase
18:18:27 <moneromooo> :|
18:18:35 <hyc> time for you to drop ccache from yout path for a while :P
18:18:48 <moneromooo> I meant I would not squash them into the relevant earlier commit.
18:18:57 <hyc> ohh
18:19:17 <hyc> I thought you meant you would stop and fix all the annoying slowdowns as you encounter them
18:19:33 <moneromooo> Ah. Well, I did that too a year or two back.
18:19:55 <moneromooo> The dude who did hte ccache patch seemed to have more experience than me with this though.
18:20:58 <hyc> I don't change branches much these days. I just have multiple worktrees from a single repo, one for each branch I'm working on
18:26:37 -xmr-pr- 00-matt opened pull request #6747: cmake: Use job pool feature to limit concurrent jobs
18:26:37 -xmr-pr- > https://github.com/monero-project/monero/pull/6747
18:26:37 -xmr-pr- jagerman opened pull request #6746: Fix broken multisig pubkey sorting
18:26:37 -xmr-pr- > https://github.com/monero-project/monero/pull/6746
19:05:04 <binaryFate> People who help with reproducible builds: please make a PR to the gitian repo. It provides a hash *signed* with your key (unlike confirming on IRC or reddit). And gives public auditability of the hashes confirmations.
19:05:27 <sethsimmons> I don't have PGP setup... Need to do that first.
19:05:33 <moneromooo> (and makes monero-update see and use it)
19:08:55 <binaryFate> It's ok to post hashes on IRC/reddit only (without signed PR), but I cannot rely only on that. That is not what users will expect me to have checked.
19:10:19 <binaryFate> I need enough people to make the effort to PR to gitian, which provides PGP-signed vetting from them (not just their IRC account saying something) and auditability in the future on why I decided that sign off on certain hashes.
19:10:33 <binaryFate> *to
19:10:47 <sethsimmons> I'll work on getting mine setup over the next couple of days when I have time.
19:10:54 <sethsimmons> Thanks for the push.
19:13:05 <binaryFate> Right now I'm asked to sign something because selsta plus 3 people on IRC confirmed it. Apart from a small epsilon, it's basically the same as trusting selsta only. IRC is not PGP.
19:32:08 <caralho> seems legit
19:44:51 <hyc> added my sigs https://github.com/monero-project/gitian.sigs/pull/61
19:54:10 <iDunk> Another set of sigs from a person on IRC is up.
22:38:32 <selsta> .merges
22:38:32 -xmr-pr- 6500 6542 6546 6593
22:53:25 <TheCharlatan> bit late again with my build, but will have sigs up soon and then merge.
22:54:01 <selsta> TheCharlatan: did you see moos message?
22:55:44 <TheCharlatan> The one asking if me is me?
22:55:46 <moneromooo> TheCharlatan: also FYI: https://github.com/monero-project/monero/pull/6745
22:55:50 <moneromooo> Yes.
22:55:57 <selsta> 14:17 <+moneromooo> If so, mind commenting on https://github.com/monero-project/monero/pull/6337, the last tweak to which removes an addition you made to fix cross compilation ?
22:57:12 <iDunk> Btw, I tested with  set(CMAKE_SYSTEM_PROCESSOR ${CMAKE_HOST_SYSTEM_PROCESSOR} CACHE STRING "" FORCE)  today.
22:58:05 <TheCharlatan> moneromooo do you mean the patch that iDunk commented?
22:58:13 <moneromooo> Yes, I did.
23:00:04 <selsta> moneromooo: I think you were talking about https://github.com/monero-project/monero/pull/6337/files#diff-657e89b8cdcca8c4852e0f983b61ec17L66
23:00:13 <selsta> not iDunk’s patch
23:01:33 <TheCharlatan> Ah, I see
23:02:38 <binaryFate> <hyc> added my sigs https://github.com/monero-project/gitian.sigs/pull/61 <-- thanks hyc and iDunk
23:07:45 <moneromooo> I meant the line vtnerd removed, but iDunk found a way to fix it since then.
23:09:00 <iDunk> Windows builds would not use supercop code anyway, with that (UNIX AND...) bit.
23:10:02 <iDunk> The benchmark with supercop code segfaults on Windows, from either MSYS2 or depends builds.