04:17:13 <hyc> uff. just noticed, i2p-zero process size is 5.8GB. 1.5GB resident. that's more than monerod is using
04:17:22 <hyc> on my public node...
04:17:47 <hyc> I'll never understand people writing network utilities in java
04:18:13 <hyc> or any system programming, for that matter.
04:20:14 <hyc> how do you expect to get any adoption if your router uses more system resources than the application it's there to support
12:15:19 -xmr-pr- selsta opened pull request #7038: build: prepare v0.17.1.4
12:15:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7038
12:15:29 <selsta> v0.17.1.4 merge list: 7018 7024 7026 7028 7037 7038
12:15:41 <selsta> xiphon: please open 7018 and 7024 against release branch
12:30:19 -xmr-pr- xiphon opened pull request #7040: [release-v0.17] rpc: skip non-synced bootstrap daemons in --no-sync mo...
12:30:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7040
12:30:20 -xmr-pr- xiphon opened pull request #7039: [release-v0.17] cryptonote_core: dandelion++ - use median remote block...
12:30:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7039
12:32:51 <xiphon> selsta: done
12:32:57 <selsta> ty
14:10:22 <selsta> 7038 7039 need an approval
14:14:52 <selsta> afterwards we can tag I think
14:55:58 <hyc> issue #7029 needs to be addressed.
14:56:07 <hyc> this appears to be a regression in 17.1.3
14:56:20 <hyc> whatever change was made probably should be reverted
14:58:58 <hyc> adding a new field, as in PR#7030 seems like the wrong fix. it is still a breaking change in the RPC API.
15:13:30 <selsta> do we know it is from v0.17.1.3? I thought the regression was from v0.17 overall
15:15:19 -xmr-pr- lh1008 opened issue #7041: Error: Error mining to daemon: Found nonce, but daemon errored out wit...
15:15:20 -xmr-pr- > https://github.com/monero-project/monero/issues/7041
15:16:05 <hyc> hmmm, trying to see the commit history
15:16:13 <hyc> looks like this actually hasn't changed since 2018 at least
15:16:35 <hyc> the issue seems invalid
15:16:54 <selsta> yea I don’t think target height ever worked this way
15:17:11 <selsta> 7030 should still be fine, just not for this release
15:17:23 <hyc> it is definitely not OPTIONAL in the definition
15:17:30 <hyc> I think the doc update was just wrong
15:18:25 <hyc> monero-site commit 746a5ffb4
15:28:53 <selsta> Guest20675: ^
15:31:37 <hyc> updated the ticket. at most, a doc fix is needed to correct the description in sync_info, the value is not optional
15:54:01 <xiphon> hyc: "adding a new field, as in PR#7030 seems like the wrong fix"
15:54:20 <xiphon> ^ what is the correct way at the moment to check if a node is synced or not via RPC?
15:54:47 <xiphon> i don't see any legit/documented way to do that
15:56:40 <xiphon> or should we explicitly say that "you have to deduce the node sync status by looking at the target_height"
15:58:41 <selsta> yea that's why we should add 7030
15:59:02 <selsta> just not for necessary for release branch IMO
16:01:07 <hyc> as discussed in that ticket - when a node is sync'd, target_height is zero.
16:12:54 <LyzaL> maybe a separate issue but my node is fully synced rn and my target height is like 130 blocks lower than my actual height, which seems weird
16:14:12 <moneromooo> Most people get it wrong. Target height is a sync mode variable. It has no meaning after you're synced.
16:18:11 <hyc> then perhaps the code in core_rpc_server.cpp should be fixed to explicitly report zero when node is sync'd
16:18:35 <hyc> or get_target_height should be fixed to return 0 in that situation
16:59:31 <ErCiccione> selsta hyc: got it. I'm gonna update the docs.
17:03:23 <hyc> cool
17:11:01 <ErCiccione> https://github.com/monero-project/monero-site/pull/1328
17:23:38 <Snipa> .merges
17:23:38 -xmr-pr- 6747 6826 6829 6830 6849 6856 6858 6873 6892 6895 6898 6903 6913 6915 6920 6921 6922 6924
17:23:47 <Snipa> Oooft, looks like I've got some catching up to do.
21:51:14 <luigi1111w> .merges
21:51:14 -xmr-pr- 6747 6826 6829 6830 6849 6856 6858 6873 6892 6895 6898 6903 6913 6915 6920 6921 6922 6924
21:51:22 <luigi1111w> for both?
21:51:34 <selsta> these merges are not urgent
21:51:37 <selsta> release has a separate list
21:51:58 <luigi1111w> yes can do tomorrow
21:59:41 <selsta> .merge+ 6937 6943 6949 6954 6960 6971 6973 6995 6999 7008
21:59:41 <xmr-pr> Added
22:00:11 <selsta> hyc: the "better log message anon networks" PR is also ready I assume? if yes then we can also include it in the release
22:07:27 <selsta> ok will conflict with https://github.com/monero-project/monero/pull/7018
22:08:41 <selsta> .merge+ 6897
22:08:41 <xmr-pr> Added
22:09:44 <hyc> selsta yeah it will conflict
22:10:08 <selsta> guess we should merge yours today
22:10:15 <selsta> so that xiphon can rebase afterwards for tomorrow
22:10:19 <hyc> ok
22:12:48 <selsta> ok luigi1111w please merge 7007 7011 today so that we avoid a conflict
22:21:17 <selsta> thanks