--- Log opened Sat Feb 16 00:00:51 2019
00:57 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning
00:57 < m-schmoock> cdecker: my server irssi session rebooted this night, if you tried to answer my question please re-do...
01:16 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
01:39 < fiatjaf> nothing happened here during the night
01:57 < m-schmoock> thx.
02:31 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:52 < m-schmoock> cdecker: Im getting to it... :D
02:58 <@cdecker> Thanks for the script t0mix, I might consider porting that to a plugin, if that's ok with you
02:59 <@cdecker> fiatjaf: exit 1 is the signal we use for all non-normal exits. There was a bug that swallowed the error messages, and I think that got fixed on master
03:00 <@cdecker> You might want to increase logs to `--log-level=debug` 
03:00 < m-schmoock> cdecker: it seems like fiatjaf is still having this issue
03:00 < m-schmoock> dunno why or if he use old binary because his buoild crashed or something
03:01 <@cdecker> m-schmoock: re your JSON controller: I think the way you describe it is correct: update local datastructures, then tell channeld to send a new channel_update
03:01 <@cdecker> Alternatively gossipd could also do that
03:01 < m-schmoock> yes, im exactly doing that now
03:02 < m-schmoock> is it correct that once I updated the channel via gosspid, the listchannels command should already have the correct values?
03:02 <@cdecker> It should, yes. We inject our own gossip messages into gossipd right away
03:03 < m-schmoock> your test framework is quite nice btw
03:06 <@cdecker> Thanks, lots of iterations got us here :-) I still think we need to cut down on the repetition in some places, but I'm quite happy too ^^
03:28 < t0mix> cdecker, it's more than okay with me. it would be a honour =D
03:28 < t0mix> an*
06:45 -!- Kostenko [~Kostenko@185.183.106.228] has quit [Remote host closed the connection]
07:57 < m-schmoock> cdecker: im now adding a new wire message type to ./channeld/channel_wire.csv  in oder to be able tell the channeld for a user specific feerate update
09:51 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
10:44 < fiatjaf> I'm not using an old binary, I've checked that multiple times.
10:44 < fiatjaf> wait, I didn't
10:47 < fiatjaf> yeah, I was using an old binary.
10:48 < fiatjaf> dang, if only I had checked that instead of trusting my own recompilation memories.
10:48 < fiatjaf> sorry to bother you.
11:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
11:22 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
11:46 < m-schmoock> fiatjaf: no worries, I was really sure it was an old binary :D
11:46 < m-schmoock> because I found the bug couple of days ago
11:49 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
11:59 < fiatjaf> now this new binary prints hundreds of memory leak warnings and closes with error 23 when I call 'stop'
13:45 < m-schmoock> nice :D   https://www.youtube.com/watch?v=3WAOxKOmR90
13:45 < m-schmoock> nothing to worry about 
13:45 < m-schmoock> you just compiled master? because im also running on master with little trouble...
14:18 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:28 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:10 -!- Kostenko [~Kostenko@bl5-167-188.dsl.telepac.pt] has joined #c-lightning
15:20 < fiatjaf> m-schmoock, just compiled master. my previous problems (absence of logs) disappeared.
15:20 < fiatjaf> have you tried stopping the daemon with 'stop'?
15:21 < fiatjaf> would it be of any help if I pasted the output somewhere?
15:25 < m-schmoock> fiatjaf: /msg ?
15:32 < fiatjaf> you're kidding me, now I've tried again and don't get the errors anymore
15:34 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
15:34 < fiatjaf> sent you the stuff I was getting before. basically that same thing repeated dozens of times.
15:35 < fiatjaf> perhaps you could just ignore me since the problem vanished.
15:40 < m-schmoock> kk
15:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
16:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:20 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds]
16:24 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:30 < m-schmoock> cdecker: can you have a look at a commit? I added the channeld wiremessage. it generates fine but when the tests are linked with ld it gives 'undefined reference' to my new wire function 'towire_channel_json_feerates'. what am i missing?    https://github.com/ElementsProject/lightning/pull/2342/commits/e4094705c9f0a44b80d621415a2459beb3a9d500 
16:31 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:31 < m-schmoock> its someting with the test framework that it doesnt like my modification in the wire.csv, and its to late for me to figure out. gn8
17:02 -!- Kostenko [~Kostenko@bl5-167-188.dsl.telepac.pt] has quit [Quit: Leaving]
17:34 -!- Kostenko [~Kostenko@bl5-167-188.dsl.telepac.pt] has joined #c-lightning
21:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
--- Log closed Sun Feb 17 00:00:52 2019