02:43:23 <gingeropolous> damn. xmrchain node got killed again. im running gdb, but it says the program no longer exists. i think its getting oom killed but i don't know why
02:46:15 <gingeropolous> i guess i can run it with the tagged release and see if it still happens
02:47:24 <m-relay> <o​frnxmr:xmr.mx> How much resources is that node using
10:38:12 <m-relay> <g​ingeropolous:monero.social> currently using 25G of ram
10:53:06 <m-relay> <g​ingeropolous:monero.social> im gonna limit the number of peers. i had inc at unlimited and outgoing at 126
11:12:32 <m-relay> <g​ingeropolous:monero.social> hrm, trying to add block message to testnet blocks to test forking behavior, getting this "Failed to load data from /miner_conf.json" buwut
12:50:41 <m-relay> <o​frnxmr:xmr.mx> Bro u dont need > 32 outgoing
12:51:09 <m-relay> <s​yntheticbird:monero.social> I need it as im building a super node thx for worrying tho
12:51:11 <m-relay> <o​frnxmr:xmr.mx> And dont really need > 100 in either
12:51:57 <m-relay> <o​frnxmr:xmr.mx> Unlimited peers is probably what killed it https://github.com/monero-project/monero/issues/9334
17:12:03 <m-relay> <t​zadiko:matrix.org> https://github.com/monero-project/monero/pull/9875
17:14:14 <m-relay> <s​yntheticbird:monero.social> oh my good Tzadiko stop cooking! 🔥🔥🔥
17:22:14 <NorrinRadd> praise good 
17:22:21 <m-relay> <t​obtoht:monero.social> tzadiko: please force-push changes to prs instead of adding commits. non-squashed prs are less likely to get reviews and will not be merged as-is. if you have a gpg key, please sign your commits. if your pr is still a wip, convert it to a draft.
17:41:38 <selsta> having unlimited incoming peers is default and should not be an issue. >32 out is excessive but also should not cause issues
17:44:11 <m-relay> <t​zadiko:matrix.org> Ok, thanks. This workflow is new to me.
17:45:43 <m-relay> <t​obtoht:monero.social> np, if you have questions feel free to ask here or dm me anytime
17:48:55 <m-relay> <o​frnxmr:xmr.mx> <s​elsta> having unlimited incoming peers is default and should not be an issue. >32 out is excessive but also should not cause issues << its (iirc) unlimited to prevent privacy issues from sybils, but definitely causes huge increases in resources
17:49:28 <m-relay> <o​frnxmr:xmr.mx> Btc and other chains default to ~115 max incoming and, iirc, 8 or 12 out
20:01:34 <m-relay> <t​obtoht:monero.social> tag still on for today?
20:02:39 <m-relay> <o​frnxmr:xmr.mx> I'm falling asleep
20:14:42 <selsta> i run all my nodes with unlimited incoming peers and no resource issues
20:15:38 <selsta> we can tag today but i feel there are multiple issues remaining (ginger having issues with blockchain explorer, offn having chain sync freeze multiple times)
20:15:42 <gingeropolous> selsta, yeah but are your nodes the target of skiddies
20:15:47 <selsta> but maybe we just have to tag at some point
20:21:00 <m-relay> <s​yntheticbird:monero.social> it's enough, we need to tag
20:25:26 <m-relay> <s​yntheticbird:monero.social> Frankly, this is embarrassing that a release is delayed again and again and again because of unidentified bug. There is at least one vuln in the wild right now, the current branch is capable of syncing and is pretty much stable for everyone. We need to tag or otherwise we're slowly turning into a grub2 situation
20:27:16 <m-relay> <s​yntheticbird:monero.social> delaying is giving no benefit at this point because of how large the difference is between 18.3.4 and 18.4.0
20:27:45 <m-relay> <s​yntheticbird:monero.social> waiting have no benefits
20:30:24 <m-relay> <r​4v3r23:monero.social> chill, that means theyll just tag 18.4 knowing full well 18.4.1 is incoming right away
20:31:11 <m-relay> <s​yntheticbird:monero.social> yeah i would like too hope in two weeks, but the reality is that 18.4.1 could come in another 3 months
20:31:26 <m-relay> <r​4v3r23:monero.social> no reason to knowingly schedule 2 back to back releases
20:32:11 <m-relay> <s​yntheticbird:monero.social> you don't know its going to be back to back
20:32:22 <m-relay> <s​yntheticbird:monero.social> right now we're taking a month to correct a bug on the TODO list
20:32:46 <m-relay> <s​yntheticbird:monero.social> so with gingerpolous and ofrnxmr having bug we haven't even identified i don't expect this to be fixed in weeks
20:33:03 <m-relay> <r​4v3r23:monero.social> you dont know thats not. if you leave identified bugs open then you need another release sooner rather than later
20:33:31 <m-relay> <r​4v3r23:monero.social> and if a point release IS months away, best to make 18.4 as stable as possible
20:35:03 <m-relay> <s​yntheticbird:monero.social> Hard disagree, a release should be delayed because another one is coming a month after, really it's some grub2 tier scheduling here.
20:35:13 <m-relay> <s​yntheticbird:monero.social> a month is long
20:35:24 <m-relay> <r​4v3r23:monero.social> wut
20:35:31 <m-relay> <s​yntheticbird:monero.social> 18.4.0 should have been released back in 2024
20:36:15 <m-relay> <r​4v3r23:monero.social> just build the release branch? you dont need cores permission
20:36:33 <m-relay> <r​4v3r23:monero.social> its not a hard fork release
20:36:35 <m-relay> <s​yntheticbird:monero.social> lmao
20:37:04 <m-relay> <s​yntheticbird:monero.social> you know well 99% of people aren't updating unless we told them to do so, and they need to update
20:37:16 <m-relay> <r​4v3r23:monero.social> 99% of people arent complaining here
20:37:18 <m-relay> <r​4v3r23:monero.social> its literally just you
20:37:21 <m-relay> <r​4v3r23:monero.social> so run the branch and chill
20:37:30 <m-relay> <r​4v3r23:monero.social> this was directed at YOU
20:37:33 <m-relay> <s​yntheticbird:monero.social> you are misinformed
20:37:39 <m-relay> <r​4v3r23:monero.social> cool
20:37:47 <m-relay> <r​4v3r23:monero.social> because we arent on your schedule lmao
20:37:54 <m-relay> <r​4v3r23:monero.social> have a good day
20:38:06 <m-relay> <s​yntheticbird:monero.social> whatever, agree to disagree
20:47:52 <NorrinRadd> yeah, since the fix is not identified, and there's an exploit in the wild, yes should ship asap 
20:48:12 <m-relay> <o​frnxmr:xmr.mx> Tbf, i have not tested to see if my bug hits on 18.3.4
20:48:14 <NorrinRadd> there's no telling when the fix will be idenfied & merged. should ship asap 
20:48:27 <m-relay> <o​frnxmr:xmr.mx> he exploit only effects _public_ rpc node
20:48:39 <m-relay> <o​frnxmr:xmr.mx> Most of which are already running the fix
20:48:53 <selsta> having a major release that freezes or crashes is worse than a RPC vulnerability in my opinion since it can also possibly impacts p2p nodes
20:49:15 <m-relay> <t​obtoht:monero.social> gingeropolous: is this the same box that was thought to have potential hardware issues? or was that ruled out
20:49:19 <selsta> either way with such a large release we will have a .1 follow up so I will ask luigi to tag
20:52:22 <m-relay> <o​frnxmr:xmr.mx> Ginger and i have different issues. Both of which coukd be hardware related, and reproducing isnt easy. For mine, i have to (and have) resynced the chain like 30x, and hit the bug probably 10+% of the time.
20:53:03 <m-relay> <o​frnxmr:xmr.mx> I think gingers node is being killed from same issue that caused selstas OOM - tx propagation
20:53:49 <m-relay> <o​frnxmr:xmr.mx> Ginger having over 1 thousand connections (iirc) means he's one of very few nodes with that many
20:54:31 <m-relay> <o​frnxmr:xmr.mx> Most others usually top out at 100-300  (i think)
21:06:46 <selsta> tx propagation causing OOM is only relevant if there is a huge txpool backlog
21:09:56 <m-relay> <o​frnxmr:xmr.mx> Isnt it simple a product of txpool size * connections
21:10:37 <m-relay> <o​frnxmr:xmr.mx> So 10mb * 100 connections == 1mb * 1000 connections (forgive me)
21:11:38 <selsta> only outgoing connections are relevant from what I remember
21:15:51 <selsta> luigi1111: you can tag whenever you have time
21:15:54 <m-relay> <b​oog900:monero.social> outgoing connections have a longer queue timer (on average), but inbound connections still have the queue.
21:16:19 <m-relay> <b​oog900:monero.social> longer queue timer = more time to build up txs in it
21:16:38 <selsta> (v0.18.4.0) also please ping me once done so I can update gui
21:25:33 <luigi1111> K
21:38:14 <m-relay> <s​yntheticbird:monero.social> luigi-chad.gif
23:14:16 <m-relay> <o​frnxmr:xmr.mx> If only luigi1111 could see that