-
hyc
of course, now that I've tweaked that message, all my tor connections are staying up
-
hyc
sheesh
-
xmr-pr
hyc opened pull request #7007: Better log message for unusable anon networks
-
xmr-pr
-
selsta
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
-
selsta
not sure why it didn’t work for me
-
viperperidot[m]
Thanks for the --ban-list option, goodbye asshoe nodes!
-
xmr-pr
hyc opened pull request #7008: Silence stupid warnings
-
xmr-pr
-
xmr-pr
vtnerd opened pull request #7009: Change epee binary output from std::stringstream to byte_stream
-
xmr-pr
-
Inge-
so 0.17.1.4 is just GUI update?
-
selsta
yes
-
hyc
is there going to be another v0.17 point release?
-
xmr-pr
hyc opened pull request #7011: Better log message for unusable anon networks [release]
-
xmr-pr
-
xmr-pr
hyc opened pull request #7010: Add rpc-restricted-bind-ip option [release]
-
xmr-pr
-
hyc
hmm
-
hyc
lost my voice in #monero and -markets
-
fluffypony
it was pointed out on Reddit that we have totally different instructions for Tor in the README and in the ANONYMITY_NETWORKS doc
-
fluffypony
-
fluffypony
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?
-
dEBRUYNE
I think the former is mostly for running the daemon over Tor, whereas the latter is for sending transactions over Tor
-
dEBRUYNE
Would prefer to put this message on the mailing list btw ->
paste.debian.net/hidden/210c433e
-
hyc
The README is pretty lengthy now, putting all the info in ANONYMITY_NETWORKS would be a good idea regardless
-
gingeropolous
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?
-
dEBRUYNE
The thread that is linked has a lengthy list of protections
-
gingeropolous
indeed
-
xmr-pr
jonathancross opened issue #7012: Wallet UX: sign_transfer should accept path to unsigned monero tx file
-
xmr-pr
-
xmr-pr
jonathancross opened issue #7013: Wallet started with --offline option showing "Error: wallet failed to ...
-
xmr-pr
-
xmr-pr
jonathancross opened issue #7014: Wallet UX: `set ask-passsword never` doesn't work as expected.
-
xmr-pr
-
binaryFate
The DNS record for auto-update are updated
-
binaryFate
*records
-
hyc
so what's get_target_blockchain_height() actually returning?
-
hyc
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
-
hyc
status
-
hyc
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
-
hyc
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
-
hyc
why is the target height smaller than the actual height?
-
tobtoht
^ I've wondered this as well
-
hyc
I think there's a problem with this commit f90bbe2a5c
-
hyc
in drop_connection() it checks for the max remote blockchain height in the current zone
-
hyc
and if there are no viable connections in the zone, it sets target height to zero
-
hyc
but this is incorrect if there are other zones that are still alive
-
hyc
so target_height is being dropped back on failures, but much further than it should be
-
moneromooo
target height is the highest known height of your peers when in sync mode.
-
selsta
hmm my node crashed with "corrupted size vs. prev_size"