--- Log opened Tue Mar 24 00:00:31 2020
01:33 -!- slivera [~slivera@217.138.204.100] has joined #joinmarket
02:35 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Ping timeout: 240 seconds]
02:37 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket
02:41 < waxwing> what continues to bother me is the 'could not find a change address' error that is popping up. that is suggesting to me that your rpc calls are not working.
02:41 < waxwing> also i'm completely lost after a very detailed debugging session yesterday, you're now saying that even though you switched your backend node, you magically didn't need to rescan to see the balance.
02:42 < waxwing> that just doesn't sound right at all. if you have used a wallet, and you move it to a new node, you definitely have to rescan, to see the balance.
02:42 < waxwing> tlo1337, ^
02:42 < waxwing> stuff about how you configure IRC is of course orthogonal to all this
03:45 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket
04:06 -!- Pinkie38Hoeger [~Pinkie38H@ns334669.ip-5-196-64.eu] has joined #joinmarket
04:23 -!- fiatjaf1 is now known as fiatjaf
05:20 < waxwing> AlexCato if you get a chance today, could you try again with the latest version of the same file i've just uploaded. i'll try and do a test on an old debian (9) *ova i have lying around, shortly.
05:22 < waxwing> for logging purposes this is what i used: staticx -l ../../jmvenv/lib/libsodium.so.18 -l /lib/x86_64-linux-gnu/libnss_dns.so.2 -l /lib/x86_64-linux-gnu/libresolv.so.2 -l /lib/x86_64-linux-gnu/libnss_files.so.2 joinmarket-qt joinmarket-qt-static
05:46 < tlo1337> i'm not getting the "could not find change address" pop-up anymore as i mentioned above
05:47 < tlo1337> i didn't end up switching the node to the second one, i ended up putting the original RPC creds in
05:48 < tlo1337> hopefully it's a little more clear now on what occured waxwing
05:49 -!- Pinkie38Hoeger [~Pinkie38H@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 260 seconds]
06:28 < waxwing> tlo1337, well not really, per se, but to boil it down: rpc creds either work or they don't. what you describe sounds like something that was discussed (i think, here) some months ago: someone with a resource constrained device, having rpc calls fail intermittently.
06:28 -!- slivera [~slivera@217.138.204.100] has quit [Ping timeout: 240 seconds]
06:29 < waxwing> i suspect there might be something specific related to the `import` call that happens when we request a change address, in the way that call specifically is coded/wrapped that means it doesn't gracefully retry. if someone wants to look at that it'd be appreciated.
06:29 < waxwing> for anyone confused what rpc calls have to do with getting a new address, the answer is that we must import addresses at the time they are requested, into the core wallet, to ensure they are there before funds are received.
06:30 < waxwing> the stuff about IRC is mostly orthogonal. note that connection failures to IRC are entirely normal and are handled by the application.
06:31 < waxwing> when using Tor, you might have an issue with v3 onion addresses (the very long onion addresses) if on an old OS distro. you'd have to handle that separately, or disable the IRC server that uses the v3 onion address.
06:38 < tlo1337> thank you for the explanation that makes sense. if i do switch to different RPC creds i'll have to do a rescan then is that correct?
06:39 < tlo1337> okay i'll keep an eye out for any issues with v3 onion addresses. so far i keep getting not enough liquidity errors, but i solved that before by being patient and at least it keeps regenerating txns and retrying
06:43 < DSRelBot> [DS/AlexCato1] RPC creds just authenticate that you're allowed to connect to the bitcoin core instance you configured - changing those RPC creds will not need a rescan. Rescans are only needed if you connect to a *different* bitcoin core instance (which generally will have different RPC creds though)
06:59 < waxwing> (does anyone know, is there a scenario where specifically `import` rpc calls will fail if a node is 'out of sync' as in struggling to keep  up with the head of chain? that might explain why people are reporting rpc failures *specifically* at tx creation time)
06:59 < waxwing> i mean i say "people" but i've only seen it reported maybe 3 times.
07:16 < tlo1337> okay so i will need to do a rescan if i were to switch to my other node because it's a different core instance with different RPC creds, if im following correctly
07:18 < tlo1337> when i switch to my other node, i will try replicating to see if i get that again
07:41 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
07:42 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
07:47 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Ping timeout: 256 seconds]
08:35 < waxwing> i see openoms is talking about 'automated joinmarket installation' on twitter. isn't the installation already automated? isn't that kinda the whole point of all the work we did over like 2 years on installation? (especially arubi). i must have misunderstood something i guess?
08:45 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket
08:49 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
08:55 < grubles> maybe it just runs the script for you
08:55 < grubles> so you save 0.1 seconds
09:21 < waxwing> i was wondering if it was something to do with the RPi? like, are there specific things you need to do there.
09:35 < waxwing> AlexCato : i got a fresh debian 10 from: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.3.0-amd64-netinst.iso and tried that in Virtual Box.
09:35 < waxwing> everything seemed to run correctly, including wallet recover, sync and single full coinjoin over irc.
09:36 < waxwing> i did see, as you mentioned, a ton of fontconfig errors on the console and one "module failed to load", but none of it seemed to affect the app.
09:36 < waxwing> (with the latest version uploaded today as per above)
09:37 < waxwing> oh and i keep forgetting, i will PR the fix for that "exit" error later today (it's got nothing to do with binary build i think)
09:58 -!- MaxSan [~four@185.9.19.107] has joined #joinmarket
10:22 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Remote host closed the connection]
10:22 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket
10:24 -!- Guest10977 [~britoair@90.162.99.55] has quit [Ping timeout: 250 seconds]
10:25 -!- rdymac_ [~britoair@90.162.99.55] has joined #joinmarket
10:29 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
10:45 -!- Netsplit *.net <-> *.split quits: tlo1337, treyzania, achow101, deafboy, kanzure
10:45 -!- Netsplit over, joins: kanzure
10:45 -!- Netsplit over, joins: treyzania, tlo1337, achow101, deafboy
11:27 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
11:39 -!- trotski2000_ [uid206086@gateway/web/irccloud.com/x-bxgcctbjrwpsxsol] has joined #joinmarket
11:44 -!- MaxSan [~four@185.9.19.107] has quit [Ping timeout: 264 seconds]
12:57 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
13:33 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
13:33 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
13:50 -!- slivera [~slivera@217.138.204.74] has joined #joinmarket
14:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
14:46 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection]
15:36 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
16:06 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.7.1]
17:24 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
17:38 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
17:43 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Ping timeout: 265 seconds]
18:17 -!- rdymac [uid31665@gateway/web/irccloud.com/x-gbgwxyxkfuywvgir] has quit [Quit: Connection closed for inactivity]
18:56 -!- HackRelay [~jmrelayha@p5DE4A3AE.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
18:57 -!- DSRelBot [~DSRelBot@p5DE4A3AE.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
19:09 -!- DSRelBot [~DSRelBot@p5DE4A2DC.dip0.t-ipconnect.de] has joined #joinmarket
19:11 -!- HackRelay [~jmrelayha@p5DE4A2DC.dip0.t-ipconnect.de] has joined #joinmarket
19:37 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
19:42 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has quit [Ping timeout: 246 seconds]
20:11 -!- rdymac [uid31665@gateway/web/irccloud.com/x-lggebkbqmlgblefg] has joined #joinmarket
23:27 -!- rdymac [uid31665@gateway/web/irccloud.com/x-lggebkbqmlgblefg] has quit [Quit: Connection closed for inactivity]
23:32 -!- jungly [~jungly@host73-184-dynamic.250-95-r.retail.telecomitalia.it] has joined #joinmarket
--- Log closed Wed Mar 25 00:00:33 2020