--- Log opened Sun Nov 22 00:00:24 2020 00:13 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning 00:48 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 256 seconds] 00:55 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning 01:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning [] 01:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning 02:24 -!- liberliver [~Thunderbi@dynamic-078-054-124-102.78.54.pool.telefonica.de] has joined #c-lightning 02:28 -!- liberliver [~Thunderbi@dynamic-078-054-124-102.78.54.pool.telefonica.de] has quit [Ping timeout: 240 seconds] 02:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 03:13 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 03:16 < darosior> You can ? 03:18 < jasan> :-) 03:18 < jasan> wrong window maybe? 03:22 < zmnscpxj__> maybe out of resources? channels can have a limit on number of HTLCs in-flight, also each HTLC reserves funds for its fees 03:22 < zmnscpxj__> ...what topic are we talking about anyway? 03:36 < darosior> I was answering az0re's question 03:37 < zmnscpxj__> well, yes, my understanding as well is similar, it should be doable 03:37 < zmnscpxj__> unless you run out of resources like I mentioned 03:37 < zmnscpxj__> but if you are rebalancing distinct different pairs of channels it "should" work. 04:23 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-lecmkndyxyxbgylp] has quit [Quit: Connection closed for inactivity] 04:23 -!- jasan [~j@n.bublina.eu.org] has left #c-lightning [] 04:23 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning 04:37 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Read error: Connection timed out] 04:37 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 05:29 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 06:15 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 06:34 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 06:43 -!- jasan [~j@n.bublina.eu.org] has quit [Quit: Will be back] 06:43 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning 06:44 -!- jasan [~j@n.bublina.eu.org] has quit [Client Quit] 06:45 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning 06:48 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 07:23 -!- jasan [~j@n.bublina.eu.org] has quit [Quit: jasan] 07:30 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 08:37 -!- jasan [~j@n.bublina.eu.org] has joined #c-lightning 08:39 < az0re> darosior: Orly? 08:39 < az0re> When I try, using `lightning-cli`, they are processed one-at-a-time 08:40 < zmnscpxj__> (*cough* clboss-movefunds *cough*) 08:41 < darosior> hehe, i really need to give clboss a try :) 08:41 < zmnscpxj__> I guess the root cause is that the python plugin framework is synchronous by default? 08:42 < darosior> az0re: lightning-cli is a ""single-threaded"" interface to the jsonrpc server, you can just use for example `lightning-cli rebalance &` for your command to be processed in background 08:42 < zmnscpxj__> do note that `clboss-movefunds` is a "best effort". also the command returns immediately 08:42 < darosior> Or ctrl-Z + bg, or a script, or w/e 08:42 < zmnscpxj__> the plugin itself is async? 08:43 < darosior> Hmmm 08:44 < zmnscpxj__> az0re could you try `lightning-cli` in mujltiple terminals simultaneously? 08:44 < darosior> It's not but i was under the impression doing this parallelized the calls :/ Maybe it's just an impression 08:45 < zmnscpxj__> my hazy understanding is that the plugin framework is sync by default and would ignore other requests while a function invoked by an exposed command has not returned 08:46 < zmnscpxj__> I vaguely remember an old issue where somebody was asking for an async plugin framework 08:47 < zmnscpxj__> az0re: why are you manually managing channel balances? CLBOSS is not managing it well? 08:48 < darosior> Yeah, and we have the async_[method] version of the methods 08:49 < darosior> (in pyln) 08:52 < darosior> Ok so we are definitely not (https://github.com/ElementsProject/lightning/blob/66b2bb9a90c5cbb83dd510fbcb450104cb4712d5/contrib/pyln-client/pyln/client/plugin.py#L541-L570) and i just fooled myself thinking this :sob: 08:52 < zmnscpxj__> ah, yes 08:55 <@cdecker> For context: the pyln library is sync, and the `async_*` style decorators pass a future `request` in so you can not return immediately. They are not related to asyncio, since we didn't want to lock in on a specific reactor, but the futures, with callbacks are easily adapted to async/await style flows 08:55 < zmnscpxj__> ah, I misremembered --- `clboss-movefunds` blocks until the move completes. but it works async since the entire plugin is async 08:56 < m-schmoock> cdecker: I fixed the broken plungin drain tests. This was because pyln changed... https://github.com/lightningd/plugins/pull/161 08:56 < zmnscpxj__> yes, I meant async as in using some kind of callback-equivalent facility, which futures are 08:58 < m-schmoock> that would reduce some of the Travis issues... 08:58 < m-schmoock> that ACK was quick :D 08:59 < m-schmoock> in the past doing 1376453msat * 0.01 * 42.0 did work and cut of any sub-msat values 08:59 < m-schmoock> but this changed sometime 08:59 < zmnscpxj__> Maybe due to `Decimal`? 08:59 < zmnscpxj__> <--- not a pythonist 08:59 < m-schmoock> not sure if fixing this by casting is the right way. maybe we can allow Millisatoshi(123.00001) 08:59 < m-schmoock> not sure 09:00 < m-schmoock> anyway 09:00 < m-schmoock> just my two millisatoshi ^^ 09:00 < az0re> darosior, cdecker: So, currently no way around it? But it should be set up to be properly async in the future? 09:00 < az0re> zmnscpxj__: Haven't set up CLBOSS yet, also a bit wary of having my funds automatically managed :) 09:00 < darosior> Currently no, i think the rebalance needs some work anyways and that it's part of it :) 09:01 < az0re> OK I see 09:01 < az0re> (it also needs multi-part payments) 09:02 < zmnscpxj__> CLBOSS splits funds movements, though not quite multi-part, since it treats funds movement as a "best effort" anyway 09:02 <@cdecker> az0re: you can do async things with the current pyln framework: mark a function as `async_method` or `async_hook`, get a `request` from the framework (which is later used to return the result), stash it somewhere (run on another thread, start an async task, ...) and return from the function (the request will stay open until you either call 09:02 <@cdecker> `request.set_result` or `request.set_failure`) 09:02 < zmnscpxj__> meaning it thinks it is okay for part of the fund being transferred to succesfully transfer while the rest does not transfer 09:02 < m-schmoock> cdecker: wtf now travis gives me AttributeError: 'LightningNode' object has no attribute 'fundchannel' 09:02 < zmnscpxj__> !! 09:03 <@cdecker> lol, you need LightningNode.rpc.fundchannel 09:03 < m-schmoock> which pyln-client version should I go for ? 09:03 < m-schmoock> nah 09:03 < m-schmoock> I want the helper 09:03 <@cdecker> We only have helper functions on LightningNode for a couple of very specific things 09:04 < m-schmoock> its only testcode 09:04 < az0re> cdecker: OK, got it, but using lightning-cli, even in the background or in multiple terminals, is not currently set up to do it--right? 09:04 <@cdecker> For some reason the helper on LightningNode (that accepts another LightningNode as arg) is called openchannel or open_channel... 09:04 <@cdecker> az0re: if the plugin is using this async + stash + later respond setup you can have an arbitrary number of concurrent lightning-cli calls, no problem 09:05 * m-schmoock is confused 09:05 < m-schmoock> can you point out on github whats the deal :D 09:05 < zmnscpxj__> `fund_channel` is how I remember it, but could be wrong 09:05 < m-schmoock> I thougt also updating requirements.txt to a newer version is sufficient 09:06 < az0re> cdecker: So, sorry for needing some hand holding here, why does it not work in parallel when I launch two rebalance commands in two terminals? 09:06 <@cdecker> So there's the `openchannel` helper which really should be called `fundchannel` for consistency: https://github.com/ElementsProject/lightning/blob/master/contrib/pyln-testing/pyln/testing/utils.py#L630 09:06 < az0re> It apparently is using that async-ish setup 09:06 < zmnscpxj__> az0re: because the plugin cannot handle it in parallel 09:07 < az0re> Oh, I think I get it; it's also the plugin logic that needs to handle async execution, and `rebalance` doesn't support it 09:08 <@cdecker> Exactly: def rebalance (https://github.com/lightningd/plugins/blob/master/rebalance/rebalance.py#L122-L123) is marked `@plugin.method` and not `@plugin.async_method`, hence everything has to happen on the main thread 09:08 < zmnscpxj__> yes 09:08 < az0re> Gotcha 09:08 < az0re> Thanks cdecker and zmnscpxj__ 09:08 < zmnscpxj__> np np np 09:08 < zmnscpxj__> also, CLBOSS :P 09:08 < az0re> One of these days... :) 09:09 < zmnscpxj__> CLBOSS is your fault. You were asking lots of questions on how to start up a node and I thought... why is there not a program that does it for new users? 09:09 < zmnscpxj__> haha 09:09 < zmnscpxj__> and thus CLBOSS was born 09:12 < az0re> You're welcome 09:12 < az0re> :P 09:12 < zmnscpxj__> hahahahaha 09:12 < zmnscpxj__> :P 09:12 < az0re> No really, I appreciate it and will try it out. "Sometime soon" ;) 09:12 < zmnscpxj__> sure sure 09:12 < zmnscpxj__> hopefully recent releases are better 09:13 < zmnscpxj__> e.g. I caught a recent bug where a rebalancer could get "chained" into moving funds from one channel to another repeatedly 09:13 < zmnscpxj__> which means I need to make a release soon instead of procastinating 09:13 < zmnscpxj__> hmmm 09:19 < m-schmoock> cdecker: why am I no longer supposed to use the fundchannel helper (non-RPC) on a plugin testcase? Or do I get something wrong? Updateing to pyln-client 0.8.2 didnt help 09:20 < m-schmoock> im lost :D 09:21 < m-schmoock> should I just swtich to rpc.fundchannel and be done? 09:22 < m-schmoock> I did use testing utils in plugin tests which contains fundchannel 09:31 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 09:34 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 09:38 -!- fiatjaf [~fiatjaf@2804:7f2:2a88:96ec:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 240 seconds] 09:40 -!- fiatjaf [~fiatjaf@2804:7f2:2a88:96ec:ea40:f2ff:fe85:d2dc] has joined #c-lightning 09:41 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 09:46 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal] 09:46 <@cdecker> No, what I meant is that we broke our naming convention for the helper and it's called openchannel instead 09:47 < m-schmoock> ah wait. so for the test helpers its now openchannel 09:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning [] 09:47 <@cdecker> Yep 09:48 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning 09:48 < m-schmoock> will try 09:54 -!- ksedgwic [~ksedgwic@192-184-134-31.fiber.dynamic.sonic.net] has joined #c-lightning 09:57 < m-schmoock> cdecker: can you quickly point out whats the difference between fundchannel and openchannel? They should both be accessible for testing. fundchannel would give me the scid whereas openchannel address and fundingtx id 09:57 < m-schmoock> also why does Travis forbid me using fundchannel when its in the same scope as openchannel 10:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 10:09 < m-schmoock> updated. lets hope its now green 10:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 10:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 10:26 < m-schmoock> cdecker: okay. drain tests are now good. #161 and #159 will fix certin issues. But theres still test_summary issues which started to fail recently. Will fix that too, but tomorrow 10:26 < m-schmoock> after that plugin suite should bee green again 11:19 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 240 seconds] 11:20 -!- jonatack [~jon@134.19.179.179] has joined #c-lightning 11:21 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 11:36 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds] 11:53 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 12:10 -!- jasan [~j@n.bublina.eu.org] has quit [Quit: Bye!] 12:22 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 12:22 -!- Netsplit *.net <-> *.split quits: early 12:25 -!- Netsplit over, joins: early 13:12 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 14:11 -!- HelloShitty [~androirc@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 14:11 < HelloShitty> Hello peeps 14:11 < HelloShitty> I had to reinstall my whole OS 14:11 < HelloShitty> And I'm getting an error while compiling c-lightning 14:11 < HelloShitty> In make command 14:13 < HelloShitty> It says: 14:13 < HelloShitty> ./bin/sh: 1: ./tools/autogen.sh: not found 14:13 < HelloShitty> And 14:14 < HelloShitty> make: *** [external/Makefile:82: external/jsmn/jsmn.c] Error 1 14:14 < HelloShitty> And lastly 14:15 < HelloShitty> ./bin/sh: 1:.. /../libbacktrace/configure: not found 14:52 < HelloShitty> niftyney cdecker darosior 14:53 < HelloShitty> niftynei 14:53 < HelloShitty> Why can't I compile this thing? 15:03 -!- HelloShitty [~androirc@bl20-171-222.dsl.telepac.pt] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )] 15:04 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 15:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 15:33 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 15:34 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 15:35 -!- psysc0rpi0n [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 15:35 -!- psysc0rpi0n is now known as HelloShitty 15:39 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Client Quit] 15:41 -!- psysc0rpi0n [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 15:46 < psysc0rpi0n> guys, when anyone can, please take a look at these compilation errors of c-lightning 15:47 < psysc0rpi0n> https://paste.debian.net/1173910/ 15:47 -!- psysc0rpi0n is now known as HelloShitty 15:47 < HelloShitty> I can't go over this point 15:48 < HelloShitty> I already installe jq as jsnm is json related, but still no good 15:59 < HelloShitty> I'll come here again tomorrow 15:59 < HelloShitty> to ask for help on that issue 15:59 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Quit: leaving] 16:05 -!- psysc0rpi0n [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 16:06 -!- psysc0rpi0n is now known as HelloShitty 16:09 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 16:19 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds] 16:30 -!- HelloShitty [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Ping timeout: 264 seconds] 16:33 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 16:35 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 16:36 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 16:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:17 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has quit [Quit: Leaving] 17:18 -!- ctrlbreak [~ctrlbreak@159.2.182.106] has joined #c-lightning 17:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:35 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 17:38 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 17:38 -!- vasild_ is now known as vasild 17:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has left #c-lightning [] 17:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-lsntjcdlexygkbwj] has joined #c-lightning 18:11 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 18:12 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 18:51 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 19:54 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 19:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 23:42 -!- psysc0rpi0n [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 23:42 -!- psysc0rpi0n [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has quit [Client Quit] 23:43 -!- psysc0rpi0n [~psysc0rpi@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 23:52 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning --- Log closed Mon Nov 23 00:00:24 2020