02:18:55 <mnt_grrrl> what is the status of .9?
02:21:03 <Snipa> .merges
02:21:04 -xmr-pr- 7248 7261 7262 7263 7264 7268 7269 7271 7272
02:24:35 <selsta> Snipa: please don't merge the last two yet
02:24:45 <selsta> others are fine
02:24:57 <Snipa> Argh.
02:25:02 <Snipa> Caught me right as I pushed.
02:25:12 <selsta> np
02:25:22 <selsta> it is not wrong
02:25:26 <Snipa> Only got the master one in, the release-17 isn't shoved up yet.
02:25:27 <selsta> so we can fix it tomorrow
02:25:57 <Snipa> 7248 is fine I assume?  Saw there was some comments on it that felt more pending-ish.
02:26:11 <selsta> better wait with it
02:26:16 <Snipa> kk.
02:27:09 <Snipa> So other than 7248 and 7272 we're good to merge for the release-17 branch?
02:27:33 <selsta> moneromooo: can you PR the new commit from 7248 as a separate one? (unknown command size limit)
02:27:44 <Snipa> If so, I'll get those cleaned up at the least, so there's less to review next cycle.
02:28:25 <selsta> yep should be good
02:28:31 <selsta> I tested them for the past days
02:28:35 <Snipa> kk.
02:28:54 <selsta> gui is good to merge
02:31:27 <selsta> mnt_grrrl: mostly testing, these rushed releases make it super easy to introduce new bugs
02:32:15 <selsta> you can compile release-v0.17 if you want the release esrly
02:32:20 <selsta> early*
02:32:26 <Snipa> .merges
02:32:26 -xmr-pr- 7248 7272
02:32:28 <mnt_grrrl> selsta, I am happy to help alpha/beta test if that would ever help
02:32:35 <Snipa> K, so that should be those two left for final conifms.
02:32:57 <selsta> ty
02:34:00 <mnt_grrrl> I will go ahead and built it now then
03:37:58 <dgoddard> I know it's super trivial and not critical, but could this PR be merged? https://github.com/monero-project/monero/pull/7240
03:46:44 <gingeropolous> lulz. i thought the --args in the example your provided iDunk was for if you wanted to pass args to gdb. sigh.
03:47:06 <selsta> dgoddard: it will be merged but we usually wait 10 days on non urgent PRs
03:47:18 <dgoddard> Got it, TY
05:13:25 <gingeropolous> damn. ok, i just compiled v0.17 release, and set it to sync from an exclusive local node running last point (v0.17.1.8). Somehow its getting host denied
05:14:13 <gingeropolous> however, the release branch i compiled hours ago when i had to pull the PRs myself managed to stay connected to this exclusive node and is still syncing
05:14:31 <hyc> what patches are new since then?
05:14:51 <gingeropolous> well, also the just compiled one is truly using the local exclusive node.
05:15:07 <gingeropolous> and the local node isn't reporting the just compiled node on the bans list
05:15:14 <gingeropolous> so i have no idea how its being blocked.
05:15:30 <gingeropolous> hah! the just compiled node banned the local node it was syncing from!
05:15:39 <gingeropolous> wtf
05:16:16 <gingeropolous> ok, ima resync the node i compiled earlier today and pass the exclusive node argument properly in gdb this time
05:17:29 <hyc> fwiw my v0.17.1.8 node + locking fix finally finished a full sync from scratch
05:17:34 <hyc> I'll build release branch now
05:17:37 <gingeropolous> and that one is on the zfs file system across the 7 shitty ssds and made it to 2187324 and is still going
05:22:14 <gingeropolous> but i just restarted it
06:06:35 <hyc> is this warning legit? https://paste.debian.net/1179609/
06:14:23 <hyc> ok, running release-v0.17 syncing from scratch again
06:14:31 <hyc> against a v0.17.1.8 node
12:37:15 <moneromooo> selsta: I removed it now
14:25:05 <hyc> ok, my build of f3de67bc2159960377845271f2657aa6b552e4b3 is at 99% after 8 hours
14:25:10 <hyc> looking good so far
14:25:50 <hyc> 1339 blocks left to go
15:05:52 <selsta> 06:15 <gingeropolous> hah! the just compiled node banned the local node it was syncing from! <-- there are some false positives during sync, which usually don't matter if you sync up from more than one node
15:06:54 <selsta> afaik this release removes one false positive case but there are more to do
15:08:39 <hyc> fully sync'd in 8hrs 54min
15:09:19 <hyc> downloaded about 71GB
15:09:47 <hyc> (looking at byte/packet counts on the interface since I started)
15:12:56 <hyc> also sent about 395MB, 5 million packets
15:13:26 <hyc> that seems excessive for downloading 2.2 million blocks
15:14:54 <hyc> set 5067251 packets, received 50542586 packets
15:15:01 <hyc> maybe it's all just ACKs
16:11:02 <normo> exit
18:55:01 <KingBong420> Hey, careful, man, there's a beverage here!
22:46:05 <mnt_grrrl> are there specific location where hosts are needed currently?
22:59:04 <mnt_grrrl> sethsimmons, can I get the link to your setup guide please?
23:00:23 <nioc> https://sethsimmons.me/guides/run-a-monero-node/
23:05:49 <mfoolb> sethsimmons: I see you modified the RuntimeDirectory=monero in the systemd script.. I was going to comment on reddit but this time I doulble checked :)
23:07:26 <sethsimmons> Yeah, thanks for the tip mfoolb!
23:07:26 <sethsimmons> Made me learn how that arg works 🙂
23:07:50 <sethsimmons> <mnt_grrrl "are there specific location wher"> You could look at something like Monero.FYI and pick a geography that is relatively bare.
23:08:08 <sethsimmons> But in general I’d just say spin one up where it’s useful for you.
23:11:19 <mnt_grrrl> sethsimmons, thank you also a vote for adding tor and i2p to your setup guide
23:15:15 <Kronovestan> I don't think I can get "in connections" on tails OS for monerod. Or can you?
23:50:02 <sethsimmons> <mnt_grrrl "sethsimmons, thank you also a vo"> Will try to, I haven’t done either myself but will try to piece something together.