Jeremy Rand
Okay. Unfortunately my ISP doesn't have IPv6 support, so this is going to be hard for me to reproduce/debug.
9b0773cf2bf139eafe4a828c8964461d34ea9e23 appears to be a relevant upstream commit, but we already merged that and it should be in `nc3.3.9.1`
@gits7r Did you enter the IPv6 address with or without the enclosing brackets? It looks to me like upstream Electrum changed the IPv6 address parsing in master branch (hasn't gotten...
@gits7r It looks like d430ec4bfc2d4ffb7b43ae63297fa9fa492aac01 and a13344938f0f8308651612efc86921a0e9b97602 from upstream are relevant; they're only in `master` branch of upstream. I've just cherry-picked them to `master-3.3.10`; can you check whether it's fixed...
Seems like cert pinning is another example of something that could benefit from Electrum being aware of which server names are actually the same server. However, it's also conceivable that...
I asked about this today on Electrum's IRC channel; no replies yet.
@gits7r Were you changing the server by choosing a different entry in the server list, or by editing the server/port text boxes?
@gits7r Which Python version were you testing with? The fact that this is related to a `CancelledError` makes me wonder if this is an instance of https://github.com/spesmilo/electrum/issues/5798 (which only impacts...
Having no luck reproducing this on Whonix 15, even if I deliberately disconnect the network connection while syncing.
@gits7r When you encountered this, did you have a SOCKS proxy enabled in Electrum-NMC? Wondering if maybe the bug is dependent on that.