01:01:49 <selsta> .merge+ 7292 7285
01:01:49 <xmr-pr> Added
01:12:32 <selsta> .merges
01:12:32 -xmr-pr- 7285 7286 7287 7292
01:39:28 <selsta> Snipa: luigi1111w: please do merges and tag v0.17.1.9 afterwards
01:46:49 <Snipa> .merges
01:46:49 -xmr-pr- 7285 7286 7287 7292
01:47:03 <Snipa> All clear for all merges, or do I need to watch my step again selsta?
01:50:54 <selsta> all good
01:55:59 <Snipa> https://github.com/monero-project/monero/tree/v0.17.1.9
01:56:03 <Snipa> Tag is hot and spicy.
01:56:17 <Snipa> And properly signed this time. :)
02:03:43 <selsta> ^ for those doing reproducible builds
02:22:46 <iDunk> I just had this  https://paste.debian.net/hidden/cca52451/
02:22:54 <iDunk> Maybe a fluke, restarting.
02:26:24 <selsta> hmm weird
02:26:53 <selsta> depends CI did build fine for all OS as far as I can see
02:29:50 <selsta> as far as I can see none of the code in make_new_connection_from_peerlist has recently changed
02:42:40 <iDunk> It built on the second run.
02:42:44 * iDunk shrugs
02:53:49 <mnt_grrrl> Copyright (c) 2014-2020 The Monero Project year is wrong
02:53:50 <one-horse-wagon> When starting up monerod, I got the idea of using two flags--ban block_tor.txt and --enable-dns-blocklist at the same time.  Good idea or not?
02:54:43 <one-horse-wagon> Thought it would make a more profound filter of bad i.p.'s out there.
03:07:53 <selsta> one-horse-wagon: you can use both
03:17:35 <one-horse-wagon> Terrific!
03:40:58 <iDunk> https://paste.debian.net/hidden/d4dd48e2/
03:56:51 <gingeropolous> i got "failed to find tx meta: <2cc1e94f " on .9
03:57:07 <selsta> yes, this exists for a while
03:57:34 <gingeropolous> ok, thanks. just confirming its something familiar.
03:57:59 <selsta> yea it is harmless and we should fix it in the future
03:59:09 <gingeropolous> ok. xmrchain is on self compiled .9
04:20:26 * Franck[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/eDbtPQELBQYTlDjGDqZWHvWT/message.txt >
04:29:41 <selsta> Franck[m]: daemon has "print_tx" function, not sure about RPC
04:31:34 <Franck[m]> Thanks selsta , good to know. At this stage I assume that my software only has access to `monero-wallet-rpc` and was hoping to find a way so I can keep this infra requirement.
05:17:39 <gingeropolous> all right 1:18 of uptime
09:41:59 <sech1> My reproducible build hashes: https://paste.debian.net/1180151/
09:43:19 <hyc> just started building here
09:45:22 <sech1> running .9 with block.txt (no tor blocking), so far so good
09:53:23 <dEBRUYNE> sech1: Does it also run properly without the block.txt file?
09:54:02 <sech1> I can try
09:55:13 <sech1> running without the block list
10:02:35 <hyc> I would guess it's pretty effective, but the auto-bans only last 24 hours
10:02:50 <hyc> I see Host unblocked and then a minute later Host blocked
10:03:01 <hyc> same hosts keep coming back
10:03:32 <hyc> 2021-01-08 07:34:07.789 I Host 49.51.155.129 unblocked.
10:03:40 <hyc> 2021-01-08 07:40:57.758 I Host 49.51.155.129 blocked.
10:04:06 <selsta> Chinese IP, could be that they have horrible latency.
10:04:20 <selsta> I also constantly see that IP, it is not an attacker.
10:04:27 <hyc> oh well
10:09:08 <sech1> I see one Chinese IP too, constantly getting unblocked and then blocked
10:09:27 <sech1> on the other hand, it happens only once a day, so I don't have much action in the logs anyway
10:09:41 <binaryFate> how does it get unblocked so quickly?
10:09:54 <sech1> ?
10:10:03 <sech1> it's unblocked after 24 hours, but blocked quickly
10:10:15 <binaryFate> ah ok
10:11:17 <sech1> speaking of blocks: https://paste.debian.net/hidden/fbf7b394/
10:11:26 <sech1> FUK's nodes are getting blocked
10:17:55 <dEBRUYNE> sech1: thanks
10:22:34 <hyc> ok my linux builds just finished, matches sech1 hashes
10:22:40 <hyc> android building now
10:22:57 <sech1> there are also iDunk's hashes: https://paste.debian.net/hidden/d4dd48e2/
10:23:00 <sech1> mine match 100%
10:23:23 <hyc> cool
10:23:47 <hyc> if one of ours didn't match at this point I suppose it would mean one of our machines was compromised
10:24:30 <sech1> Or unstable overclock :D
10:26:00 <hyc> heh
10:26:17 <hyc> ok I just started it up on my VPS, without ban list
10:28:07 <sech1> My PC is overclocked btw, but it's stable enough to run xmrig 10M benchmark correctly several times and pass Testmem5 anta777 extreme preset
10:28:16 <sech1> insta reboot with Prime95 though :D
11:01:04 <Snipa> Sashed from my build: https://paste.debian.net/1180164/
11:01:07 <Snipa> *Hashes.
11:07:38 <hyc> so far so good. android & freebsd matched too. windows building now
11:08:55 <binaryFate> Please sign your hashes when you paste them, otherwise it's only as solid as your IRC account security
11:08:58 <Snipa> PR up, includes my key, same as the one used to sign the main Monero repos.
11:11:56 <sech1> How to sign? I don't even have keys generated
11:12:16 <binaryFate> sign with a key that is in the gitian repo
11:12:24 <binaryFate> if you have one
11:12:44 <sech1> I probably don't
11:13:06 <binaryFate> useful without anyway no biggy, just better for those who can
11:13:31 <Snipa> https://paste.debian.net/1180165/
11:13:42 <Snipa> Resubbed w/ signature and XMR block hash for time/date verification.
11:13:57 <sech1> I'll try to add my keys for the next release
11:14:09 <sech1> Is it done here https://github.com/settings/keys ???
11:14:20 <Snipa> Fork the main gitian.sigs repo, PR w/ your key
11:14:37 <Snipa> Ala: https://github.com/monero-project/gitian.sigs/pull/130/files
11:14:47 <Snipa> https://github.com/monero-project/gitian.sigs/pull/131/files is mine that includes my key with this build.
11:15:01 <sech1> I'll try later today
11:16:27 <sech1> I only started doing these builds because I didn't want to wait for the release :D
11:18:10 <Snipa> Trying to be more active and not work 24 hours a day at the $dayjob.
11:32:20 <hyc> I wonder what version of MacOS SDK we'll need to build Apple ARM64 binaries
11:32:33 <hyc> all my builds done, hashes match
12:16:21 <selsta> https://github.com/bitcoin/bitcoin/pull/20880 <-- this is also something we can look into for monero
12:20:14 <selsta> though looks quite complicated, not sure if worth the effort, we already sign the GUI anyway
12:47:29 <binaryFate> Binaries for new version 0.17.19 are available on getmonero.org, great job everyone!
12:48:05 <binaryFate> *0.17.1.9
12:53:28 <gingeropolous> xmrchain  uptime 0d 8h 46m 53s
12:53:28 <gingeropolous>  on .9
12:57:52 <selsta> gingeropolous: "The most up to date software for Monero are version"
12:58:01 <selsta> looks like this can also be updated :D
13:01:43 <gingeropolous> yeah yeah yeah
13:02:42 <gingeropolous> there we go :)
13:52:35 <sethsimmons> Thanks for all the hard work on .9, everyone! Running great on all my nodes without the Tor banlist so far.
14:56:39 <mj-xmr_> I'd say, that the parallel tests are ready from my side. Everybody's points have been addressed one way or another.
14:56:40 <mj-xmr_> https://github.com/monero-project/monero/pull/7283
14:57:25 <fluffypony> mj-xmr_: dumb question maybe (because I haven't looked at it yet) but it doesn't parallelise performance tests right?
14:57:55 <mj-xmr_> uhm... good point
14:57:59 <mj-xmr_> it does.
14:58:49 <mj-xmr_> But they can be launched sequentially as well. The framework allows this.
14:59:29 <selsta> for CI performance tests are not that interesting
14:59:37 <selsta> at least I don’t look at them
15:01:21 <fluffypony> I mean, for CI we can skip performance tests for sure
15:01:43 <fluffypony> (unless we want to have a performance pipeline to pick up regressions, but we're not exactly ingesting test data in graylog or anything)
15:04:53 <mj-xmr_> I see, that the master doesn't call performance tests in the CI either (not through ctest at least)
15:05:20 <mj-xmr_> 22 tests in both cases, and none of them is performance test, or is it a range of tests with some name prefix?
15:05:33 <selsta> might be that make release-test does not run them
15:06:24 <mj-xmr_> https://github.com/monero-project/monero/pull/7289/checks?check_run_id=1663049254 Click on Tests, and page down
15:06:38 <mj-xmr_> To see the test logs
15:11:30 <mj-xmr_> "make test" (which is an alias for ctest), only calls these executables, which are tagged as add_test(TARGET)
15:11:57 <mj-xmr_> If the performance tests are python scripts, or sth, they have no chance of being picked up by ctest.
15:13:03 <selsta> ok, then we can ignore it anyway
15:16:40 <fluffypony> https://github.com/monero-project/meta/blob/master/SERVER_SETUP_HARDENING.md
15:16:45 <fluffypony> the server setup / hardening guide is up
15:17:22 <fluffypony> would love any additional input from infosec people in the room
15:17:23 <fluffypony> cc SerHack
15:29:45 <mj-xmr_> I'm giving up on the proposed ML based ban solution for now. Firstly I see, that you're doing a great job on fighting off the attack, and secondly there's still a lot to do on the CI part, and this is my bag of tea.
16:09:58 <ErCiccione[m]> fluffypony: That's very useful. Thanks!
16:30:29 <gingeropolous> alll right 12 hrs of uptime on xmrchain.net
16:30:59 <binaryFate> without banlist?
16:31:17 <gingeropolous> with banlist
16:31:38 <gingeropolous> i might as well fully test in production eh?
16:32:29 <gingeropolous> all right, flyin hot
16:50:25 <hyc> i've been running without banlist for 6 hours. so far onlay banned 1 IP, the one from CHina
16:54:14 <sech1> My node keeps banning FUK's nodes, 71 so far after 7 hours
17:18:43 <M5M400> oh. time for .9?
17:18:53 <dEBRUYNE> it's out already :-P
17:18:54 <dEBRUYNE> M5M400 ^
17:19:53 <M5M400> want me to spin it up on pubnode without banlist?
17:21:34 <M5M400> updated
21:15:19 <SerHack> fluffypony: whoa! it's well-written
22:27:39 <mnt_grrrl> hay could the link to the binaries get fixed so that it is not cached please
22:29:13 <binaryFate> mnt_grrrl: I believe they are fixed now, but you may still be affected by old ones that your browser has cached
22:31:56 <mnt_grrrl> oh ok thank you!
22:33:38 <binaryFate> mm good thing I checked, it seems to work for gui links but not cli
22:35:46 <mnt_grrrl> oh
22:39:20 <binaryFate> fixed now hopefully
22:39:50 <binaryFate> If you do curl -I https://downloads.getmonero.org/cli/mac64 or another one, you should see an "Expires:" field that should show the current time
22:43:11 <pink_zebra[m]> Hello, do you believe that the new law for crypto financial regulation will push more users to monero?
22:44:57 <Inge-> not a development related question. please try #monero or #monero-policy
22:45:15 <moneromooo>  /j #monero-police
22:46:12 <Inge-> ouch