--- Log opened Mon Jan 07 00:00:13 2019
00:09 <@cdecker> Or maybe scientific notation? I'd like to send 1e-11 BTC, that's very readable imho ;-)
00:09 <@cdecker> Seriously, this has been discussed so many times before, a single unit is really the wrong approach, but I do support the unit-suffixed API
00:35 < blockstream_bot> [George Vaccaro, Blockstream] Anyone else's c-lightning node burning a hole in their floor?  Mines running hot for the last hour or so. lightning_gossipd is maxing my cpu.
00:37 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning
01:10 < rusty> blockstream_bot: I've had another report of this.... have you ever used a debugger before?
01:29 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
01:29 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
01:33 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
01:33 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
01:39 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
01:39 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
01:43 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
01:43 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
01:44 <@cdecker> Alternatively we could collect a flamegraph using perf and see what is using all the cycles
01:48 < rusty> cdecker: I'm not sure why gossipd would do so much work... a backtrace would probably provide a clue.
01:49 < rusty> cdecker: any chance you can check all the typo fixes before tomorrow's IRC meeting?  https://github.com/lightningnetwork/lightning-rfc/milestone/2 I'm a bit disappointed they haven't got a second ack :(
02:00 <@cdecker> Will do, and I also have a secutity review today, but the typo review has priority
02:06 < fiatjaf> rusty, I like msatoshis, there could just be better way to make people aware
02:07 <@cdecker> rusty: do we have a meeting bot on #lightning-dev for the meeting of are we doing it ad-hoc?
02:07 < fiatjaf> suffixes are also good, if it's possible to make the default be msatoshis and the api is not broken
02:07 < rusty> fiatjaf: well, we default to satoshis for onchain stuff, and msat for lightning stuff which doesn't help!
02:08 < rusty> cdecker: I just pinged AJ who seems to run the bot which bitcoin-core-dev uses.    But I expect it might just be a little chaotic for the first one.
02:14 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
02:14 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
02:23 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
02:23 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
02:28 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds]
02:41 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:46 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:46 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:49 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
02:49 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
02:50 < bitonic-cjp> Is anyone already implementing plug-in hooks?
02:58 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
02:58 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
03:05 < fiatjaf> where can I see a list of existing plugins?
03:44 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
03:44 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
03:48 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
03:49 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
04:14 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
04:14 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
04:16 <@cdecker> bitonic-cjp: I have the `plugin-8` branch which brings the hooks API with it, but it's not yet a PR on GH
04:17 <@cdecker> You'll be happy to see that `htlc_accepted` is the very first hook I implemented
04:17 < bitonic-cjp> :-D
04:17 <@cdecker> That should finally allow you to branch out an incoming HTLC and forward it to a different instance
04:18 < bitonic-cjp> I guess I should pull that branch and evaluate it, even though I know it's a WIP.
04:19 <@cdecker> I'm still a bit unsure as to what the result from the hook should look like. Currently I'm thinking about an object with a `result` field that can be `fail`, `resolve` (with a `payment_key`) and `continue` (just do what you'd normally do)
04:21 <@cdecker> Do you think that would be sufficient for the cross-chain atomic swap?
04:22 < bitonic-cjp> I think it should be something like that. Would it make sense to give back detailed failure info? AFAIK the only thing we send back over Lightning is a failure code, so maybe that?
04:23 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
04:23 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
04:25 < bitonic-cjp> I think some use cases have errors that have a kind of a Lightning equivalent. Rejected exchange rate is kind of equivalent to insufficient fees (though not literally the same).
04:25 <@cdecker> Right, in addition we can send back a channel_update with some failure codes, but that's probably a bit too much to ask a plugin
04:25 <@cdecker> Let's keep it like this for now, extending later is easy, reducing not so much
04:26 < bitonic-cjp> ok
04:26 < bitonic-cjp> So when a plug-in says 'fail', lightningd will always send back the same error code for now?
04:30 <@cdecker> Right, I'd propose temporary_node_failure, since it is temporary, doesn't require a channel_update and can potentially be retried immediately again
04:30 <@cdecker> (retries in case we were an intermediate hop that is)
04:32 < bitonic-cjp> I'm not familiar with the full consequences of different error codes, but that sounds quite flexible indeed.
05:03 -!- deusexbeer [~deusexbee@079-170-137-113-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 246 seconds]
05:30 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:39 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
06:00 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
06:11 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
06:14 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
06:14 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
06:18 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
06:19 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
06:24 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
06:24 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
06:33 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
06:34 -!- booyah [~bb@193.25.1.157] has joined #c-lightning
06:38 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
06:39 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
06:47 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
06:54 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
06:54 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
06:58 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
06:58 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
07:04 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
07:04 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
07:13 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
07:14 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
07:20 < blockstream_bot> [George Vaccaro, Blockstream] @blockstream_bot sorry I fell asleep. Which debugger, dbg?  I've used it maybe twice but not too deep.
07:22 < blockstream_bot> [George Vaccaro, Blockstream] Sorry, I think I'm reading the thread wrong.  Anyone else having high CPU on lightning_gossipd?
07:48 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
08:24 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
08:24 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
08:24 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving]
08:28 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
08:29 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
08:54 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
08:54 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
08:58 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
08:58 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
09:04 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
09:04 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
09:08 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
09:09 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
09:19 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
09:19 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
09:23 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
09:24 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
09:29 < blockstream_bot> [Daniel Williams, Blockstream] not me. which commit are you on, @georgevaccaro?
09:34 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
09:34 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
09:35 -!- AmikoPay_CJP [~AmikoPay_@a83-163-77-195.adsl.xs4all.nl] has joined #c-lightning
09:48 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
09:48 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
10:09 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
10:09 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
10:13 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
10:14 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
10:20 < blockstream_bot> [George Vaccaro, Blockstream] I'm running stock v0.6.1
10:26 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 252 seconds]
10:26 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
10:29 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
10:29 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
10:31 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Remote host closed the connection]
10:33 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
10:34 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
10:38 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
10:54 <@cdecker> George: I think a profile might be what we're looking for, could you install the `gperf` package (assuming you are using a debian based distro)
10:56 <@cdecker> After that you can run `perf record -F 99 -p $(pgrep -f lightning_gossipd) -q -- sleep 180` and it should return after 3 minutes.
10:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 258 seconds]
10:56 <@cdecker> That'll create a perf trace that we can use to analyse where gossipd is spending time
10:58 <@cdecker> The filename is called `perf.data` and does not contain any confidential information. It'd be great if you could attach that file to an issue on Github :-)
10:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
11:09 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
11:09 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
11:13 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
11:13 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
11:39 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
11:39 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
11:48 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
11:48 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
12:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
12:19 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
12:19 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
12:20 -!- AmikoPay_CJP [~AmikoPay_@a83-163-77-195.adsl.xs4all.nl] has quit [Quit: Leaving]
12:24 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
12:28 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
12:28 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
12:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
12:59 -!- deusexbeer [~deusexbee@080-250-076-070-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
13:09 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
13:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:09 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
13:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
13:13 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
13:14 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
13:40 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
13:45 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:00 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:09 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:12 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds]
14:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:56 < rusty> niftynei: OK, I have a new version of the pay plugin for you to try f you're up for it. paystatus now works without crashing :)
15:11 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has quit [Ping timeout: 250 seconds]
15:13 -!- keymone [~keymone@31.16.193.167] has joined #c-lightning
15:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:39 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:58 < niftynei> rusty sg, send it my way!
16:03 < rusty> niftynei: tests hit a fail, checking now
16:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 250 seconds]
17:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:20 -!- keymone [~keymone@31.16.193.167] has quit [Ping timeout: 244 seconds]
18:21 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has joined #c-lightning
18:41 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has quit [Ping timeout: 245 seconds]
18:43 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has joined #c-lightning
18:55 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning
19:49 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Ping timeout: 250 seconds]
20:35 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
21:03 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning
21:40 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:40 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
22:19 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
22:30 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
22:36 < blockstream_bot> [George Vaccaro, Blockstream] @cdecker Thanks for the follow up.  Sorry, I've been all over the place today.  I installed gperf and saved that command to a little script so I'll have it for next time but my node cooled off now. :(  I'm sure I'll be able to capture something though as on the server I run my node on, the fan goes nuts when this happens.  It sometimes wakes me up at night.  Next time it fires up I'll 
22:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:06 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
23:18 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
--- Log closed Tue Jan 08 00:00:14 2019