13:47:39 is docker still using bionic for builds? is that working for everyone? 14:09:38 Worked for me, and yes, bionic 14:31:38 the docker host doesn't even matter when you use dockrun, right? 14:35:33 Dockrun uses am 18.04 image 14:37:00 (i use slightly modified dockrun, since repo vers doesnt work on deb 12) 17:07:47 .merge+ 10506 10507 10508 10509 9899 17:07:47 Added 18:59:19 monero-i686-linux-gnu-v0.18.5.0.tar.bz2 doesn't repro 18:59:41 non-determinism in unbound package 18:59:59 sneedle and ofrn match, scooby doesn't 19:00:11 what about ci gitian output? 19:00:16 checking 19:02:00 i don't remember seeing unbound in updated packages 19:03:05 it wasn't updated 19:03:18 ci matches sneedle and ofrn 19:03:29 i'll ask scooby to clear cache and rebuild 19:05:52 Hi, a quick question regarding refactoring. 19:05:52 The following line in wallet2.cpp uses designated initializers: 19:05:52 src.multisig_kLRki = {.k = {}, .L = {}, .R = {}, .ki = rct::ki2rct(td.m_key_image)};[... more lines follow, see https://mrelay.p2pool.observer/e/pOK3wYALYldveVRJ ] 19:09:48 If it currently compiles on all platforms then I would keep it as is, refactoring PRs are usually not accepted. 19:11:19 we could work towards switching to c++20 on master 19:35:01 need +1 on 10509 19:36:24 I approve of the changes in 10509 19:36:33 Not sure if it counts though :( 19:48:27 jpk68: it doesn't, i'm bound to the CoC. did you try making a support ticket to get your gh account unblocked? worked for me years ago when i signed up with tor. 19:49:31 where's this cache? i'm happy to rebuild. is it inside gitrun-bionic or base-bionic-amd64? am I docker exec'ing into a shell in a container and rm'ing a directory? 19:50:32 tobtoht: Yes, I have contacted their support several times over the course of two months. I receive the exact same templated response every time 19:51:32 jpk68: ugh.. 19:51:34 I signed up with a legit resedential IP, verified with a real phone number, etc. The ban reason was for "abuse of GitHub actions" which I have never even used 19:52:08 I also tried to make a second account to get an actual support response, and it didn't do anything... plus contacting a Microsoft employee (who responded) but they couldn't do anything 19:52:21 I will stop ranting now :) 19:52:39 scoobybejesus: one sec, it's been a while since i touched gitian 19:53:56 jpk68: ok, well perhaps it's time for us to start thinking about if it makes sense to allow contributors to approve of prs via logged channels / alternative ways 19:56:03 tobtoht: Thanks, that would be hugely appreciated. Clearly I am annoyed about this primarily because it's personally inconvenient, but I think that not having other options besides GH is going to be... not a good idea in the future. But that's just me 19:56:15 <321bob321> There is an easier fix 19:57:17 <321bob321> Selfhostimg doesn't have this issue 19:58:03 @jpk68:matrix.org: Do like the bots - just create a new acct 19:59:22 scoobybejesus are you using dockrun? 19:59:33 yep 20:00:02 @ofrnxmr:xmr.mx: The stupid CAPTCHA doesn't work, no matter what I try. This has apparently been a thing since 2023 20:00:07 https://github.com/orgs/community/discussions/177816 20:00:07 https://github.com/orgs/community/discussions/57317 20:00:28 They also block Tutanota emails 20:00:42 *for new signups 20:02:23 Someone could revive tippero and add a module to allow a ack/nak command to github :D 20:02:43 (that was an old python IRC bot) 20:03:28 I pray to the gods of Core that a self-hosted Forgejo instance will be considered someday ;) 20:03:36 Hey, we might have more GitLab disk space soon anyways... 20:06:12 scoobybejesus: there should be a container called gitrun? can you delete it and rerun dockrun 20:06:34 indeed. maybe that's easiest. on it 20:09:40 > > > monero: miniupnpc.patch 20:09:40 > > > patching file src/p2p/net_node.inl 20:09:40 > > > Hunk #1 FAILED at 2989. 20:09:40 > > > Hunk #2 FAILED at 3057. 20:09:41 [... more lines follow, see https://mrelay.p2pool.observer/e/7b2hw4ALZ18wR2xZ ] 20:10:13 ravfx: yeah miniupnp is gone 20:10:35 Perfect! 20:24:13 jpk68: if github continues its steady decline in reliability we might not have a choice lol 20:24:30 someone would need to set up the infra for self-hosted runners and be willing and able to maintain it reliably tho 20:25:28 True 20:25:44 So far weve had a few self-hosted solutions come and die or decline faster than github 20:25:57 It wasn't run by Core though 20:26:24 Example: repo.getmonero.org has one job and its offline due to spam and a full disk 20:26:34 Also, Forgejo actions syntax is very similar to GitHub's and can probably be converted quickly 20:26:39 Repo.getmonero.org is managed by core 20:26:49 Well, the server is. 20:27:35 In fairness to GH, the spammers are relentless as shown by the repo.getmonero.org issues 20:28:35 GH clearly doesn't care about that, considering the amount of vibecoded garbage they push 20:28:35 There are millions of accounts of repo, and unless you manually approve each one you'll end up with people storing unsightly shit on it 20:28:43 See: GH trending page 20:29:14 Of account on repo/gitlab 20:40:07 They also apparently suspended sech1's CI usage for a few weeks last year 21:14:51 ofrnxmr: There's a reason why the big projects use a mailing list to coordinate patches 21:15:04 And just leave the self-hosted repository as invite-only 21:17:26 i agree 21:19:08 Is there something that can be set up, like a #monero-prs channel, for sending pastebin links 21:19:20 So it doesn't clutter up this one 21:32:39 pastebin banned me for uploading the uri of a base64 image (but the data redacted) so that term is triggering to me and we can't mention it anymore 21:33:01 debians* 21:34:54 In the meantime I guess I'll just put them here then (??) 21:40:54 What's wrong with sending patches over mail? 21:41:17 I don't have any problem with that. But AFAIK there isn't a mailing list 21:41:22 IRC is designed to be ephemeral so it would be harder to keep track of 21:41:35 Oh uhh Matrix too 21:41:47 They both aren't designed for this 21:42:05 I know, I was just thinking, as a temporary fix, it could work 21:42:41 I have like 6 different PRs that I want to submit right now, and it would be annoying for me to randomly paste links here 21:43:10 Annoying to others, I mean 22:02:30 Yes > <@jpk68:matrix.org> In the meantime I guess I'll just put them here then (??) 23:03:34 so this error is from trying to build on a fresh ubuntu 26.04 install: Error response from daemon: client version 1.41 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version 23:05:23 Using what method 23:05:35 dockrun.sh 23:06:32 <321bob321> Docker daemon version 23:07:13 yeah seems like 23:41:45 how weird. different i686 hash from before and still doesn't match. https://secpaste.dev/show/qenQT4ut 23:42:44 @monero.arbo:matrix.org: same error on fresh 24.04 actually 23:47:35 you gotta sudo vim /etc/docker/daemon.json and then { "min-api-version": "1.41" } and then sudo systemctl restart docker 23:48:14 we'll see if your workaround will similarly result in different i686 hashes... 23:49:29 okay yeah that did the trick, we will see 23:56:22 common: make timespan more readable https://paste.debian.net/hidden/a2e373c4 23:58:28 jpk68: we have a no code rewrite policy 23:58:44 so unless it fixes a bug it won't be merged 23:58:50 debian wont even let me view the diff cus banned lol 23:59:03 Just to be clear, it's improving the readability of the output, not how the function is written 23:59:24 will take closer look