--- Log opened Wed Jul 31 00:00:26 2019 00:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 01:10 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has quit [Ping timeout: 264 seconds] 01:24 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has joined #c-lightning 02:06 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds] 02:14 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 02:25 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds] 02:28 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 02:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 03:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 03:59 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...] 04:12 -!- spinza [~spin@102.132.245.16] has joined #c-lightning 04:49 < m-schmoock> @rusty (when he is online) im running the voodoo branch now. 04:50 * m-schmoock wonders if rusty can read this when he gets back online ... 05:36 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #c-lightning 05:37 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Client Quit] 05:44 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 05:44 < m-schmoock> what would be a good mainnet node to attrackt payment routed traffic? I did 100 tx per day in the past, but since a week or so theres currently almost no traffic... 06:01 -!- TheCharlatan [~TheCharla@109.236.87.57] has joined #c-lightning 06:03 < TheCharlatan> Is there are a reason why the --rpc-file argument is limited in length? 06:04 < TheCharlatan> I have a container that I am running somewhere deep in my GOPATH and would like to mount volumes for the rpc file in the same location. 06:07 < TheCharlatan> I can obviously alias, but I'd like to know what the reason was for this. 07:07 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 09:34 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 272 seconds] 09:44 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning 10:56 -!- michaelsdunn1_ [~michaelsd@unaffiliated/michaelsdunn1] has quit [Quit: ZNC 1.6.3+deb1+xenial0 - http://znc.in] 11:17 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 11:21 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 258 seconds] 11:24 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 11:26 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 11:53 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds] 12:01 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 13:08 -!- reallll is now known as belcher 13:51 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 14:41 < e4xit> can c-lightning plugins hook into the network/messaging system, to perform alternative routing of the HTLC messages through another band? 16:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 16:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:20 <@niftynei> rusty: question about tal. if a tal_count(obj) is erroring out on the line `check_bounds(ignore_destroying_bit(t->parent_child));` ... where should i look for a problem? 17:20 < rusty> niftynei: obj is not a tal object? 17:21 <@niftynei> it should be a tal object D: 17:21 < rusty> niftynei: ofc first stop is "run under valgrind" which will tell you if it got freed somewhere along the line. 17:23 <@niftynei> sigh. 17:23 <@niftynei> thanks! 17:23 <@niftynei> (i was afraid you were going to say that, the freed bit) 17:23 < rusty> niftynei: meh, it's trivial, valgrind will tell youe xactly where it was freed. 17:24 <@niftynei> kkk 17:25 < rusty> esp. if this is the main lightningd, just valgrind lightningd/lightningd and sit back and watch :) 17:25 <@niftynei> oh wait, do i not even need to run a test on top of it? 17:25 <@niftynei> you just run valgring on the binary? 17:26 < rusty> niftynei: well, depends how you're triggering this bug. 17:26 <@niftynei> via a protocol test? 17:27 < rusty> niftynei: OK, change the c-lightning runner to run "valgrind" in front of the binary. 17:27 <@niftynei> kk 17:28 < rusty> Yeah, at the subprocess.Popen line. Hmm, I don't *think* it will catch stderr, so you'll see it directly. 17:29 <@niftynei> no dice. 17:29 < rusty> niftynei: did you see any valgrind output at all? 17:30 < rusty> It's pretty chatty by default... 17:30 <@niftynei> https://pastebin.com/dd5n2EjZ 17:30 <@niftynei> yeah at the top 17:31 < rusty> lightning_openingd: FATAL SIGNAL 6 (version v0.7.1-233-g1121807-modded) 17:31 < rusty> You're valgrinding the wrong binary :( 17:31 <@niftynei> oh. 17:31 < rusty> Which is a bit harder, and in another way, a bit simpler :) 17:33 < rusty> mv lightningd/lightning_openingd lightningd/lightning_openingd.real; echo 'exec valgrind "$0".real' > lightningd/lightning_openingd; chmod a+x lightningd/lightning_openingd 17:33 <@niftynei> e4xit check out the `htlc_accepted` hook 17:33 < rusty> Won't survive a rebuild of cuorse. 17:36 <@niftynei> lightningd: lightning_openingd: bad version ' 17:36 <@niftynei> and then subprocess.TimeoutExpired: Command '' timed out after Could not contact lightningd seconds 17:36 < rusty> Oops. 17:37 < rusty> I forgot we use cmdline opts. 17:37 < rusty> echo 'exec valgrind "$0".real "$@"' > lightningd/lightning_openingd 17:37 < rusty> Oh, probably want to shut valgrind up, too... --quiet I think? 17:37 < rusty> So: 17:37 < rusty> echo 'exec valgrind -q "$0".real "$@"' > lightningd/lightning_openingd 17:38 < rusty> "This time for sure!" 17:38 <@niftynei> well so now it's not printing the backtrace crash at all 17:39 < rusty> ... problem fixed! ? 17:39 <@niftynei> it just shows the python level error (where it can't unpack the non-response) 17:39 <@niftynei> ahaha 17:39 <@niftynei> if the backtrace WAS the problem then yes 17:40 < rusty> Yeah, valgrind doesn't like the backtrace code. But strange you don't get an error before that... 17:40 < rusty> stderr from subdaemons explicitly gets allowed through. 17:40 <@niftynei> yeah it's just quiet 17:41 < rusty> Try running the whole thing with "LIGHTNINGD_DEV_NO_BACKTRACE=1 ..." 17:41 < rusty> That will turn off backtraces, but I'd still expect to see the error in the logs? 17:42 <@niftynei> https://pastebin.com/MfGGeee5 17:43 < rusty> /tmp/test-events-l_jbylu7/lightningd/log (IIRC)? 17:45 <@niftynei> well that's new '2019-08-01T00:40:41.448Z INFO lightningd(31906): 02c6047f9441ed7d6d3045406e95c07cd85c778e4b8cef3ca7abac09b95c709ee5 chan #1: Owning subdaemon lightning_openingd died (32512) 17:45 <@niftynei> ' 17:46 < rusty> Not surprising since it crashed... Hmm. 17:47 < rusty> OK, it *seems* like valgrind isn't seeing an error. That generally means the problem is more direct. 17:47 < rusty> Is there a branch I can look at? 17:49 <@niftynei> yep! 17:49 <@niftynei> one sec 17:50 <@niftynei> https://github.com/niftynei/lightning/blob/nifty/dual-funding/openingd/openingd.c#L2503 17:51 <@niftynei> it's the check on tal_count(state->df->their_inputs) that's failing 17:52 <@niftynei> the last time that field was touched is here https://github.com/niftynei/lightning/blob/nifty/dual-funding/openingd/openingd.c#L2349 17:54 <@niftynei> it seems fine here? https://github.com/niftynei/lightning/blob/nifty/dual-funding/openingd/openingd.c#L615 17:55 < rusty> Sorry, was wrapping up something else before I could switch my tree. Reading code in a browser sucks 17:57 <@niftynei> e4xit: check out the `htlc_accepted` hook, it's probably close to what you want 17:58 <@niftynei> oh wait, the messaging system. afaik that's not possible atm. 17:58 <@niftynei> np rusty 17:59 < rusty> Hmm, looks reasonable. 18:00 <@niftynei> i need to hop off for a bit, dog is getting very insistent about it being dinner time 18:00 < rusty> OK, time for a dumb binary search! status_trace("%u: %u", __LINE__, tal_count(state->df->their_inputs)) everywhere, see where it crashes 18:00 <@niftynei> kk! sg. i'll try that next. thanks for the assist! 19:32 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 19:35 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Client Quit] 21:31 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 246 seconds] 23:45 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds] 23:48 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning --- Log closed Thu Aug 01 00:00:27 2019