--- Log opened Thu May 09 00:00:07 2019
00:52 -!- Kostenko [~Kostenko@176.78.154.81] has quit [Remote host closed the connection]
01:25 < k3tan> t0mix, ive used it successfully as well
01:27 -!- Kostenko [~Kostenko@dsl-154-81.bl26.telepac.pt] has joined #c-lightning
01:32 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Remote host closed the connection]
01:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 268 seconds]
01:58 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
02:12 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 248 seconds]
03:14 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:37 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:45 <@cdecker> m-schmoock: found the issue that was preventing us from restarting failing plugins, it wasn't the output (which goes to stderr anyway) it was our error message when we were reading from stdout and reporting a broken pipe
03:46 <@cdecker> Added a fixup that should make restarts possible even if the first attempt fails
03:51 < m-schmoock> Nice. I will try it. Meanwhile im working on the next helpful thingy: https://github.com/lightningd/plugins/pull/22
03:51 <@cdecker> Interesting idea :-)
03:52 <@cdecker> Could be useful to aggregate sub-dust balances as well :-)
03:54 < m-schmoock> cdecker: one other stupid misuse issue with autostart, when the plugin is no longer readable (moved or so), it will log "FileNotFoundError: [Errno 2] No such file or directory" and cease to work even of the binary is restored
03:54 < m-schmoock> dont know if we should account for this fringe cases
03:55 < m-schmoock> in theory, it could recover this
03:56 < m-schmoock> the drain/fill plugin can be especially usefull if you want to remove unreliable channels but want to keep or take the liquidity onchain or not
03:57 < m-schmoock> for example a service provider gets paid a lot, he may want to close channels when they are really full not just 95%
03:57 < m-schmoock> i dont know, but im sure ppl will find it useful :D
03:58 < m-schmoock> cdecker: can you elaborate on sub-dust aggregation?
04:07 <@cdecker> If I have 10 channels on which I own 400 satoshis then closing a channel without draining into a single channel means that all my 4000 satoshi go to fees for the respective channels, while if I aggregate them all by draining them into a single channel and then close that channel I can actually keep the funds
04:09 < m-schmoock> I see ;) valid usecase. 'dust management'
04:09 < m-schmoock> cdecker: I commented your autorestart PR changes. Just a minor issue with it to increase UX
04:10 < m-schmoock> If im too picky, please forgive me
04:10 < m-schmoock> brb, lunch
05:02 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
05:05 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has joined #c-lightning
05:51 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Quit: Leaving]
05:51 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
07:24 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #c-lightning
07:25 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
07:25 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
07:30 < m-schmoock> cdecker: your autorestarter already saved me a noticable amount of time. considering networkload for gissip after each restart also network resources.
07:31 < m-schmoock> <3 you should write about this in the mailing list, as it speeds up plugin development a lot. may be intersting to people not so active in IRC
08:12 <@cdecker> Absolutely, I'll write it up and send it to the ML
08:16 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has quit [Remote host closed the connection]
08:45 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
09:06 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:19 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
09:52 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 268 seconds]
10:05 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning
10:45 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
10:59 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
11:57 < t0mix> m-schmoock, I did define PYTHONPATH env variable. as you advised for rebalance, too. but it seems not to work with "summary".
11:58 < t0mix> reading https://github.com/lightningd/plugins/blob/master/summary/requirements.txt, I did install "requests" + "packaking" using python-pip (I had no idea what I was doing).. but it didn't help, too.
12:15 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
12:17 -!- kexkey [~kexkey@5.181.233.22] has joined #c-lightning
12:20 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
12:39 <@cdecker> t0mix: any error messages when starting with the plugin configured?
12:39 <@cdecker> `lightningd` will print any exception a plugin throws in its logs, including ones that are caused when not finding the plugin executable
12:40 <@cdecker> (is the plugin file marked as executable? `chmod +x` is your friend)
12:40 < t0mix> it is executable
12:40 <@cdecker> Also the plugins rely on python3 (some may work on python2 as well, but no guarantee)
12:40 < t0mix>   File "/home/bitcoiner/.lightning/plugins/summary.py", line 3, in <module>
12:40 < t0mix>     from packaging import version
12:40 < t0mix> ImportError: No module named 'packaging'
12:41 < t0mix> then it waits for some dozens of seconds and fail to start
12:41 < t0mix> 2019-05-09T19:41:09.038Z plugin-summary.py The plugin failed to respond to "getmanifest" in time, terminating.
12:41 < t0mix> Can't recover from plugin failure, terminating.
12:42 <@cdecker>  Oh it seems to be missing a dependency
12:42 < t0mix> python 2.7.13-2
12:42 <@cdecker> Ok, you seem to have installed the requirements in python2
12:43 <@cdecker> Do you have `pip3` installed? `pip3 help` will tell you
12:43 < t0mix> pip & pip2
12:43 <@cdecker> Are you using ubuntu?
12:44 <@cdecker> (or another debian derivative?)
12:44 < t0mix> raspberian\
12:44 < t0mix> yes
12:44 <@cdecker> Ok, let me check on my rasp pi how the package is called
12:45 <@cdecker> Ok, `apt install python3-pip` will install `pip3` and then we can install the plugin dependencies
12:47 <@cdecker> Can't wait for python2 to finally be removed as a default version for python, then this whole thing is going to be easier ;-)
13:01 < t0mix> @cdecker, works like a charm! ^^ thanks!
13:02 <@cdecker> Awesome, anything we can do to improve the docs?
13:03 < t0mix> well, for people familiar with python it was probably clear what to do when reading https://github.com/lightningd/plugins/blob/master/summary/requirements.txt
13:03 < t0mix> for me it was like "wat???"
13:05 < t0mix> then m-schmoock advised to run lightning with PYTHONPATH variable. so I checked ./lightning/contrib/pylightning/README.md .. that's how I found there is such thing as "pip"
13:07 < t0mix> I'm still not sure why I'm using that variable. shouldn't I simply install pylightning with pip3, too?
13:08 <@cdecker> The variable is only needed if you want to include the source code of a dependency. The `pip3` dance is te only thing that matters :-)
13:41 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:32 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:46 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:09 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl]
16:59 -!- kexkey [~kexkey@5.181.233.22] has quit [Ping timeout: 258 seconds]
18:41 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
20:14 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
20:14 < warren> checking for passing pointers via makecontext()... sh: line 1: 24558 Segmentation fault      (core dumped) ./configurator.out 2>&1
20:14 < warren> ./configure on RHEL7 182556cfdab49a7fb33b836a9aad376d59c4df67
20:15 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 244 seconds]
22:14 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 246 seconds]
23:12 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has joined #c-lightning
23:22 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 248 seconds]
23:32 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
23:47 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
--- Log closed Fri May 10 00:00:10 2019