what is the status of .9?

.merges

Snipa: please don't merge the last two yet

others are fine

Argh.

Caught me right as I pushed.

np

it is not wrong

Only got the master one in, the release-17 isn't shoved up yet.

so we can fix it tomorrow

7248 is fine I assume? Saw there was some comments on it that felt more pending-ish.

better wait with it

kk.

So other than 7248 and 7272 we're good to merge for the release-17 branch?

moneromooo: can you PR the new commit from 7248 as a separate one? (unknown command size limit)

If so, I'll get those cleaned up at the least, so there's less to review next cycle.

yep should be good

I tested them for the past days

kk.

gui is good to merge

mnt_grrrl: mostly testing, these rushed releases make it super easy to introduce new bugs

you can compile release-v0.17 if you want the release esrly

early*

.merges

selsta, I am happy to help alpha/beta test if that would ever help

K, so that should be those two left for final conifms.

ty

I will go ahead and built it now then

I know it's super trivial and not critical, but could this PR be merged? monero-project/monero #7240

lulz. i thought the --args in the example your provided iDunk was for if you wanted to pass args to gdb. sigh.

dgoddard: it will be merged but we usually wait 10 days on non urgent PRs

Got it, TY

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

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

what patches are new since then?

well, also the just compiled one is truly using the local exclusive node.

and the local node isn't reporting the just compiled node on the bans list

so i have no idea how its being blocked.

hah! the just compiled node banned the local node it was syncing from!

wtf

ok, ima resync the node i compiled earlier today and pass the exclusive node argument properly in gdb this time

fwiw my v0.17.1.8 node + locking fix finally finished a full sync from scratch

I'll build release branch now

and that one is on the zfs file system across the 7 shitty ssds and made it to 2187324 and is still going

but i just restarted it

is this warning legit? paste.debian.net/1179609

ok, running release-v0.17 syncing from scratch again

against a v0.17.1.8 node

selsta: I removed it now

ok, my build of f3de67bc2159960377845271f2657aa6b552e4b3 is at 99% after 8 hours

looking good so far

1339 blocks left to go

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

afaik this release removes one false positive case but there are more to do

fully sync'd in 8hrs 54min

downloaded about 71GB

(looking at byte/packet counts on the interface since I started)

also sent about 395MB, 5 million packets

that seems excessive for downloading 2.2 million blocks

set 5067251 packets, received 50542586 packets

maybe it's all just ACKs

exit

Hey, careful, man, there's a beverage here!

are there specific location where hosts are needed currently?

sethsimmons, can I get the link to your setup guide please?

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 :)

Yeah, thanks for the tip mfoolb!

Made me learn how that arg works 🙂

<mnt_grrrl "are there specific location wher"> You could look at something like Monero.FYI and pick a geography that is relatively bare.

But in general I’d just say spin one up where it’s useful for you.

sethsimmons, thank you also a vote for adding tor and i2p to your setup guide

I don't think I can get "in connections" on tails OS for monerod. Or can you?

<mnt_grrrl "sethsimmons, thank you also a vo"> Will try to, I haven’t done either myself but will try to piece something together.