--- Log opened Thu Jun 03 00:00:28 2021
01:15 -!- belcher_ [~belcher@user/belcher] has quit [Quit: Leaving]
01:15 -!- belcher [~belcher@user/belcher] has joined #joinmarket
01:16 -!- belcher [~belcher@user/belcher] has quit [Remote host closed the connection]
01:17 -!- belcher [~belcher@user/belcher] has joined #joinmarket
01:39 -!- Evanito[m] [~evanitoma@2001:470:69fc:105::1ec] has quit [Quit: node-irc says goodbye]
01:40 -!- Evanito[m] [~evanito@2001:470:69fc:105::1ec] has joined #joinmarket
01:54 -!- undeath [~undeath@user/undeath] has joined #joinmarket
02:20 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has quit [Ping timeout: 268 seconds]
03:01 -!- Netsplit *.net <-> *.split quits: Anduck, berndj, dr-orlovsky, emzy, stoner19
03:11 -!- Netsplit over, joins: dr-orlovsky, berndj, stoner19, Anduck, emzy
03:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #joinmarket
03:16 -!- Anduck [~anduck@chimney.aom.fi] has quit [Ping timeout: 265 seconds]
03:18 -!- Anduck [~anduck@chimney.aom.fi] has joined #joinmarket
03:20 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has joined #joinmarket
04:15 < waxwing> undeath, as per the py3.7 requirement for ob-watcher do you think we should look to make 3.7 a requirement for whole app (py3.6 EOL end this year according to kristapsk i think), or could we just add an error message to let users know why it fails on 3.6?
04:15 < waxwing> a couple days back i had to spend a while to figure it out, as i'd forgotten what caused it and it was pretty mysterious.
04:16 < waxwing> belcher, i'm going to add a couple bits of code to the regtest setup (in particular test/ygrunner.py) so that we have a mix of FB and non-FB ygs in the test setup. that way it'll be easier to do a bunch more test scenarios.
04:16 < undeath> both is fine. some people still seem to be running py3.6 for some reason
04:16 < belcher> sounds good waxwing 
04:17 < undeath> if there are no reasons to use py3.7 code in other parts of jm maybe use a warning message for now?
04:17 < belcher> i personally couldnt get ygrunner working after i tried it once or twice, and since then tested by setting up my own bots manually (i suppose it would be better to debug and fix whatever the problem was, but you know how it is sometimes lol)
04:18 < waxwing> belcher, i know i'm repeating myself, but *please* do fix it ... you have no idea how much more productive you can be in tests if you have that set up.
04:19 < belcher> ok, noted, ill try
04:19 < waxwing> the other thing that i wondered about though: istr you saying that just running the test suite itself is slow; is that still true?
04:19 < waxwing> i mean it's a bit slow for me, like .. 5 minutes?
04:20 < waxwing> but if it's really long then i feel like we should address that. and yes CI of course, too, but that's kinda separate.
04:20 < belcher> its not particularly slow for me, its a fine speed idk
04:20 < belcher> when i develop tests i only run the test i develop on so its much faster then
04:20 < belcher> and then run the whole thing just once or twice
04:20 < waxwing> yeah true enough. it's never that big of a deal.
04:22 < waxwing> just ping me if you're having trouble running ygrunner. i have a vague memory that something was kind of bust last time we did it but that was ages ago, i'm sure we can get over it.
04:23 < waxwing> undeath, yeah a warning message. or i guess more technically, an error message, i.e. 'this is why it crashed and what you need to do to fix'
04:24 < undeath> yep, will pr
04:24 < waxwing> or huh, just check the version on startup of ob-watcher
04:24 < undeath> that was my plan
06:24 -!- Evanito[m] [~evanito@2001:470:69fc:105::1ec] has quit [Quit: node-irc says goodbye]
06:24 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has quit [Quit: node-irc says goodbye]
06:26 -!- Evanito[m] [~evanito@2001:470:69fc:105::1ec] has joined #joinmarket
06:31 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has joined #joinmarket
07:29 < waxwing> belcher, a tangentially related point, about testing: it's a shame we're only using date based locks - or am i missing a trick? - because testing the unlockability of coins is rather hard without block based locks that can be easily triggered on regtest.
07:30 < waxwing> i remember i actually tested the real timelocks when you did the original PR, on mainnet :) yolo
10:37 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.1]
11:13 < JoinMarketRelay> [hackint/rojiro] Is there also a matrix relay for this channel?
11:14 < JoinMarketRelay> [hackint/rojiro] FYI, I am sure you are aware, but this is not getting relayed over to freenode.
11:20 < Evanito[m]> Matrix relay is up, I initialized it. You can join #joinmarket:libera.chat @rojiro 
11:30 < JoinMarketRelay> [hackint/rojiro] JoinMarketRelay: is there terminal based matrix client?
11:30 < JoinMarketRelay> [hackint/rojiro] sorry i am a matrix noob
11:36 < waxwing> yeah we agreed to deliberately stop relaying to/from freenode.
11:40 < JoinMarketRelay> [hackint/rojiro] from hackint? or from matrix?
11:41 < JoinMarketRelay> [hackint/rojiro] Where should I go for the highest volume joinmarket chat?
11:43 < Evanito[m]> You are already here. The matrix room I linked is a mirror of here, if matrix is your thing. As for the client I dunno @rojiro
11:46 < JoinMarketRelay> [hackint/rojiro] oh I see. okay thanks. Note that the topic here still says it's bridged with freenode
12:57 < belcher> waxwing yes we're only using date based locks, i designed it that way because the datetime is closer to human experiance than block height
12:57 < belcher> also the value of timelocked bonds is calculated using datetime
14:43 < waxwing> belcher, i haven't really checked it out but is it possible that we could speed up the sync by disabling the burner sync for now, while it's disabled?
14:44 < waxwing> istr there's like several hundred addresses for the timelock so maybe it's irrelevant and it's mostly that.
14:45 < waxwing> re: datetime, yep i get it but it's a pretty substantial hurdle to testing. unless i missed a trick, which is possible.
16:02 < belcher> for the datetime issue you could send coins to a locktime in the past
16:02 < belcher> i think apart from that theres no way to make it easily testable, like if you wanted a utxo thats locked and later it becomes unlocked
16:02 < belcher> though i note all of this was tested when the fidelity bond wallets PR was merged
16:03 < belcher> i doubt disabling burner sync would speed it up
16:03 < belcher> waxwing ^
21:33 -!- belcher_ [~belcher@user/belcher] has joined #joinmarket
21:36 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 245 seconds]
23:30 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Quit: No Ping reply in 180 seconds.]
23:31 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #joinmarket
23:44 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Remote host closed the connection]
23:44 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #joinmarket
--- Log closed Fri Jun 04 00:00:28 2021