00:05:21 of course, now that I've tweaked that message, all my tor connections are staying up 00:05:28 sheesh 00:16:08 -xmr-pr- hyc opened pull request #7007: Better log message for unusable anon networks 00:16:08 -xmr-pr- > https://github.com/monero-project/monero/pull/7007 00:23:33 was reading through some old vtnerd comment and apparently using 2 anonymity networks should work just fine, it does not send them through both anonymity networks 00:23:37 not sure why it didn’t work for me 00:43:02 Thanks for the --ban-list option, goodbye asshoe nodes! 02:46:08 -xmr-pr- hyc opened pull request #7008: Silence stupid warnings 02:46:08 -xmr-pr- > https://github.com/monero-project/monero/pull/7008 05:01:08 -xmr-pr- vtnerd opened pull request #7009: Change epee binary output from std::stringstream to byte_stream 05:01:08 -xmr-pr- > https://github.com/monero-project/monero/pull/7009 09:16:42 so 0.17.1.4 is just GUI update? 09:24:10 yes 12:14:33 is there going to be another v0.17 point release? 12:31:08 -xmr-pr- hyc opened pull request #7011: Better log message for unusable anon networks [release] 12:31:08 -xmr-pr- > https://github.com/monero-project/monero/pull/7011 12:31:09 -xmr-pr- hyc opened pull request #7010: Add rpc-restricted-bind-ip option [release] 12:31:09 -xmr-pr- > https://github.com/monero-project/monero/pull/7010 14:05:11 hmm 14:05:23 lost my voice in #monero and -markets 14:41:25 it was pointed out on Reddit that we have totally different instructions for Tor in the README and in the ANONYMITY_NETWORKS doc 14:41:26 https://github.com/monero-project/monero/#using-tor 14:42:35 does someone want to take a stab at harmonising those two, or maybe we just nuke the "using tor" section out the README and link to the ANONYMITY_NETWORKS doc? 14:49:08 I think the former is mostly for running the daemon over Tor, whereas the latter is for sending transactions over Tor 14:52:02 Would prefer to put this message on the mailing list btw -> https://paste.debian.net/hidden/210c433e/ 15:02:33 The README is pretty lengthy now, putting all the info in ANONYMITY_NETWORKS would be a good idea regardless 15:44:28 dEBRUYNE, is it worth including in that mailing list message that ANONYMITY_NETWORKS is advised to avoid these known, inherent flaws of just relying on clearnet? 15:51:53 The thread that is linked has a lengthy list of protections 15:55:40 indeed 16:16:08 -xmr-pr- jonathancross opened issue #7012: Wallet UX: sign_transfer should accept path to unsigned monero tx file 16:16:08 -xmr-pr- > https://github.com/monero-project/monero/issues/7012 16:31:09 -xmr-pr- jonathancross opened issue #7013: Wallet started with --offline option showing "Error: wallet failed to ... 16:31:09 -xmr-pr- > https://github.com/monero-project/monero/issues/7013 17:16:09 -xmr-pr- jonathancross opened issue #7014: Wallet UX: `set ask-passsword never` doesn't work as expected. 17:16:09 -xmr-pr- > https://github.com/monero-project/monero/issues/7014 18:36:32 The DNS record for auto-update are updated 18:37:54 *records 21:17:23 so what's get_target_blockchain_height() actually returning? 21:17:25 2020-11-11 21:10:01.796 W No suitable outbound tor connections at height 2228507 - currently unable to send transaction(s) to this zone 21:17:25 status 21:17:25 Height: 2228528/2228528 (100.0%) on mainnet, not mining, net hash 1.69 GH/s, v14, 12(out)+21(in) connections, uptime 0d 6h 37m 49s 21:17:25 2020-11-11 21:13:35.166 W No suitable outbound tor connections at height 2228507 - currently unable to send transaction(s) to this zone 21:17:39 why is the target height smaller than the actual height? 21:22:35 ^ I've wondered this as well 21:24:25 I think there's a problem with this commit f90bbe2a5c 21:25:00 in drop_connection() it checks for the max remote blockchain height in the current zone 21:25:23 and if there are no viable connections in the zone, it sets target height to zero 21:25:39 but this is incorrect if there are other zones that are still alive 21:29:07 so target_height is being dropped back on failures, but much further than it should be 22:24:42 target height is the highest known height of your peers when in sync mode. 22:58:58 hmm my node crashed with "corrupted size vs. prev_size"