--- Log opened Fri Nov 27 00:00:28 2020
00:40 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
00:46 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Read error: Connection reset by peer]
00:52 -!- LiquidSnake007 [~SolidSnak@160.32.202.232] has joined #joinmarket
00:57 < LiquidSnake007> im looking for business plans/presentations for a web-based business of any sort... where can i find this? anyone know?
01:00 -!- Dylan19Schowalte [~Dylan19Sc@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 240 seconds]
01:39 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
02:27 -!- LiquidSnake007 [~SolidSnak@160.32.202.232] has quit [Quit: Leaving]
02:59 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket
03:20 -!- Harvey76Lakin [~Harvey76L@static.57.1.216.95.clients.your-server.de] has joined #joinmarket
03:27 -!- ricks_ [~ricks_@unaffiliated/ricks-/x-3439430] has joined #joinmarket
03:28 < ricks_> Hello. Is orderbook liquidity poor at the moment? I'm new to this and it is failing with n=9
03:33 < ricks_>  I'll try ob-watcher.py to understand it better. For testing, are there any expected failures? I have '24 failed, 263 passed'. If anyone is interested, I can post the output, but I do not know if it would be unsafe to show what failures happened.
03:34 < waxwing> what commit are you running on?
03:34 < ricks_> waxwing: 231779c32de5ed1a8890a0df8b88033a936d3596
03:35 < waxwing> i see. yes, we know the tests are passing on that commit, it'll most likely be a slight difference in your test joinmarket.cfg
03:35 < waxwing> which test files included those 24 failures?
03:36 < waxwing> i mean full log might be a bit overkill
03:37 < waxwing> (if you created a new wallet on that commit and didn't edit the config, you're going to have like 5 or 6 counterparties available at best, so yeah there isn't enough liquidity yet.)
03:37 < ricks_> I....also used `virtualenv --system-site-packages` when initializing my jmvenv; I'll report back with results for both my current results and results from a virtualenv that doesn't use system libs
03:37 < ricks_> > the config -- is this referring to the regtest conf, or?
03:39 < waxwing> yes, you need to move that regtest_joinmarket.cfg into your source root dir and rename it joinmarket.cfg there.
03:39 < waxwing> ie .../joinmarket-clientserver/joinmarket.cfg
03:39 < waxwing> then when you run pytest from that dir, it will get picked up there.
03:40 < waxwing> because tests automatically set the datadir flag to '.'
03:40 < waxwing> (hopefully obvious, but we do it this way to avoid the annoyance of having to mess with your real datadir which defaults to ~/.joinmarket)
03:41 < ricks_> Yes, that was done. Something I encountered was that pytest was unable to find jm{base,bitcoin,client,daemon} during testing. I had to install each module to my system. This was while I was in the jmvenv env
03:42 < waxwing> oh. yeah, clearly that's not supposed to happen. your system-site-packages choice is presumably the culprit
03:43 < ricks_> Mmmm, error was present even without using system-site-packages. I'll redo the testing but I'll uninstall jm{...} from my system afterwards to show you the errors
03:43 < ricks_> Thank you for the help, by the way
03:46 < waxwing> again, just tell me which files in the test suite have failures, that in itself is a huge clue what's wrong.
03:46 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Quit: Leaving]
03:46 < waxwing> but yeah yw. but i'm more interested in what you started out talking about, see my questions about new wallet etc.
03:46 < waxwing> also be aware that default fallback is to 4 even though we request 9.
03:47 < waxwing> see `minimum_makers` in the config
03:52 < ricks_> Alright, I'll give it a look. I tihnk I may have overwritten the last failures while running this one; bare with me here, I'll be a few minutes
03:53 < waxwing> oh, no rush at all on that.
03:53 < waxwing> i'm off for a while anyway
03:53 < waxwing> to all: merged the release notes, will build the release later today.
04:01 < ricks_> waxwing: these are the failed tests when used with system-site-packages: https://dpaste.org/6qjL/slim
04:03 < ricks_> Ah, 100% success when when not using system-site-packages...
04:08 < ricks_> Well, re: pytest not picking up jmbase even in jmvenv, that seems to have been resolved, too, even after I uninstalled jm{base,client,bitcon,daemon} from my system. Must be user-error somewhere....
04:36 < ricks_> Actually, no, I am still unable to run pytest  without having it installed in my system vs. only in the virtualenv. https://dpaste.org/FoC5
04:36 < ricks_> Main culprit being `ImportError: cannot import name 'hextobin' from 'jmbase' (unknown location) `
04:37 < ricks_> Entering python and importing from the module is fine, though..
04:45 -!- reallll is now known as belcher
05:03 < waxwing> ricks_, at first sight, that list of errors reads to me like it's running the current version of the tests, against an old version of the code.
05:04 < waxwing> where 'the code' would be whatever actual jmclient, jmbitcoin ... packages are actually being picked up
05:26 < ricks_> I'm unsure how it could be old code, I've pulled and ran `rm -r jmvenv`. Regardless, I've found a workaround for now by installing jmbase and friends to my system, I'm content knowing tests passed. I did create a new bech32 wallet following the USAGE.md instructions, but I only skimmed sourcing commitments; I'll give that a better read
05:27 < waxwing> ok, my guess is you had jmbitcoin etc. in your system site-packages, but not the latest version. since pytest is crawling '.' for tests, so the newest version, seems likely that's what's happened.
05:29 < ricks_> Oh, I didn't have jmbitcoin in my system site-packages prior to running pytest. I did that to fix the testsuite failing to find it. I also only have 0.7.2 on this system
05:30 < ricks_> (well, 0.7.2 version, master branch)
06:51 -!- ddsa12dadasddasd [3a99165c@n058153022092.netvigator.com] has joined #joinmarket
06:52 -!- ddsa12dadasddasd [3a99165c@n058153022092.netvigator.com] has quit [Remote host closed the connection]
07:06 -!- davterra [~davterra@68.235.43.94] has quit [Quit: Leaving]
07:22 < DSRelBot> [DS/visitor] Hello guys, I have faced a problem with my yield generator, I started receiving error messages, with description commitment is blacklisted. Can anyone tell me what is the problem here? I have done some transactions before without any issue
07:26 -!- davterra [~davterra@68.235.43.102] has joined #joinmarket
07:26 -!- ricks__ [~ricks_@unaffiliated/ricks-/x-3439430] has joined #joinmarket
07:30 -!- ricks_ [~ricks_@unaffiliated/ricks-/x-3439430] has quit [Ping timeout: 246 seconds]
08:22 < waxwing> 'commitment blacklisted' refers to a taker using the same commitment again, see SOURCING-COMMITMENTS.md in docs/ directory for some background. it's nothing you've done.
09:00 < DSRelBot> [DS/waxwing] test
09:01 < waxwing> belcher, i did darkscience, pls do hackint when you get a chance, thanks
09:06 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 3.0]
09:11 < d3spwn> Q: as i understand it, addresses that have been a target of a forced address reuse attack are automaticly frozen. how can in unfreeze just the non dust utxo?
09:22 -!- ricks___ [~ricks_@unaffiliated/ricks-/x-3439430] has joined #joinmarket
09:25 -!- ricks__ [~ricks_@unaffiliated/ricks-/x-3439430] has quit [Ping timeout: 265 seconds]
09:25 < ricks___> Is this kind of conf correct? I'm unsure if I should uncomment the clear net addresses. Also, is there any real world benefit running to runnning bitoind via tor?
10:02 < waxwing> d3spwn, you can just manually unfreeze any utxo you like
10:02 < waxwing> in Qt in the Coins tab, and with the 'freeze' command of wallet-tool
10:02 < waxwing> you can also set the threshold above which, even a reused address utxo will not be frozen, in the config
10:03 < waxwing> ricks___, i didn't get the context
10:28 < belcher> edited topic on hackint waxwing 
10:41 -!- Silarous [59bba534@89.187.165.52] has quit [Ping timeout: 245 seconds]
11:03 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
12:42 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
12:44 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
13:23 -!- jonatack [~jon@82.102.27.171] has quit [Ping timeout: 256 seconds]
13:24 -!- jonatack [~jon@82.102.27.171] has joined #joinmarket
13:28 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 256 seconds]
13:52 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
14:05 -!- Zenton [~user@unaffiliated/vicenteh] has joined #joinmarket
14:05 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #joinmarket
14:16 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
14:17 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #joinmarket
14:41 -!- Harvey76Lakin [~Harvey76L@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 264 seconds]
15:27 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving]
17:04 < waxwing> did anyone else have this problem? https://old.reddit.com/r/joinmarket/comments/k1w2io/error_when_trying_to_install_joinmarket_on_debian/ also see https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/737
17:04 < waxwing> note in the former i explained how i solved it on ubuntu1804 VM some months ago, but was rather mystified why it was happening.
17:05 < waxwing> please report if you can start up JM Qt on your instance debian/ubuntu, especially latest install
17:57 -!- belcher_ [~user@unaffiliated/belcher] has quit [Ping timeout: 246 seconds]
18:01 -!- DSRelBot [~DSRelBot@p5de4a6f3.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
18:01 -!- HackRelay [~jmrelayha@p5de4a6f3.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
18:12 -!- DSRelBot [~DSRelBot@p54866c8e.dip0.t-ipconnect.de] has joined #joinmarket
18:16 -!- HackRelay [~jmrelayha@p54866c8e.dip0.t-ipconnect.de] has joined #joinmarket
18:40 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Remote host closed the connection]
19:06 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket
19:55 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket
19:58 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 272 seconds]
20:07 < ricks___> waxwing: I can start JM Qt in a 20.04 Ubuntu VM, 0.7.2. This is my output, maybe if they post theirs it would show a discrepency https://dpaste.org/CEHm
20:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
20:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #joinmarket
22:14 -!- beIcher [~user@unaffiliated/belcher] has joined #joinmarket
23:19 -!- ricks___ [~ricks_@unaffiliated/ricks-/x-3439430] has quit [Remote host closed the connection]
--- Log closed Sat Nov 28 00:00:29 2020