--- Log opened Fri Dec 06 00:00:29 2019 00:10 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 00:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 00:28 -!- jamaljsr [uid406503@gateway/web/irccloud.com/x-jrvmnuvgbvootuzp] has quit [Quit: Connection closed for inactivity] 00:35 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 276 seconds] 01:08 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Quit: My MacBook has gone to sleep. ZZZzzz...] 01:10 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning 01:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:39 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has joined #c-lightning 01:47 -!- jonatack_ [~jon@213.152.162.99] has joined #c-lightning 01:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 01:49 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has quit [Ping timeout: 268 seconds] 02:09 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 265 seconds] 02:24 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning 03:12 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 03:15 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 250 seconds] 03:16 -!- reallll is now known as belcher 04:02 -!- Amperture [~amp@65.79.129.113] has quit [Ping timeout: 245 seconds] 04:26 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning 04:28 <@cdecker> MrHash: fiatjaf is probably on the right track: with the `htlc_accepted` hook you can manage invoices externally (without c-lightning knowing anything about the invoice or preimage) and then track state externally 04:29 <@cdecker> fiatjaf: keep in mind that any form of backups that are not transactional (i.e., use the db_write hook to make sure the change was written to the backup before committing to it) can potentially lead the loss of funds (the usual backup problem with LN) 04:30 <@cdecker> You could of course create a db_write plugin that keeps an append only journal on disk, sync that with syncthing and give c-lightning the go-ahead to commit only when syncthing has done its magic 04:34 < m-schmoock> cdecker: im having troubles to use wait_channel_active or wait_for(lambda: [c['active'] for c in n.rpc.listchannels(scid)['channels']] == [True, True], 600) . It never finishes (not even after 10 minutes) 04:34 < MrHash> cdecker: ok thanks i think that's a bit beyond my use case requirements at the moment but it's good to know that almost anything is possible! 04:34 < m-schmoock> (for remote channels) 04:35 < m-schmoock> which is why I currently cant test drain, as it requires gossip to be up2date 04:36 < m-schmoock> for some trange reason i cant even get it run locally 04:52 -!- jonatack_ [~jon@213.152.162.99] has quit [Ping timeout: 240 seconds] 04:56 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 246 seconds] 04:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning [] 04:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning 05:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 245 seconds] 05:28 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 05:43 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 06:06 <@cdecker> Hm, that's strange. Can you Ctrl-C and see if it really is in that wait_for statement? 06:09 < m-schmoock> cdecker: its that the result of listchannels will always return an empty array for some strange reason (for remote channels) 06:09 < m-schmoock> i printed the stugf 06:09 < m-schmoock> *stuff to the console 06:09 < m-schmoock> I now try another run where all nodes are NxM connected directed to each other, hopefully gossip is faster this way 06:10 < m-schmoock> note: `listchannels` is used withint wait_channel_active 06:10 < m-schmoock> maybe just something stupid, we should have noted already 06:13 < m-schmoock> If my struggle persists, I will submit a testcase as a PR, so you can see directly 06:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:38 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 06:39 < darosior> MrHash: I've fixed clightningjs and implemented async response to HTLC https://github.com/darosior/clightningjs/commit/16337d5ceb6c0f5523403a180d3ef2e2f1304228 06:40 < MrHash> ok awesome! thanks 06:40 < MrHash> i'll take a look 06:41 < MrHash> do you have a collection of clightningjs plugins anywhere? 06:43 < darosior> Haha no clightningjs is barely used only by me 06:43 < darosior> Ah no! It's used by RideTheLightning 06:44 < MrHash> might be an idea to add a collection to your repo no? 06:44 < darosior> I think it's preferable to use https://github.com/lightningd/plugins/ : it's not restricted to Python plugins 06:45 < darosior> Feel free to submit a PR 06:45 < MrHash> oh ok 06:45 < darosior> I'll review it 06:45 < MrHash> sure 06:45 < darosior> MrHash: Ah and I gave a look to your docker collection for setting up a lightning regtest network, good work 06:45 < MrHash> thanks 06:45 < darosior> I might use it in the near future :-) 06:46 < MrHash> sure, its handy for scripting scenarios 06:46 < MrHash> ideally i'd like to evolve it to use scaling, swarm or even kubernetes 06:47 < MrHash> i've only done all the amd64 images and a few arm images, getting around to uploading some more arm and arm64 07:03 -!- cubancorona [~cubancoro@pool-72-77-31-161.pitbpa.ftas.verizon.net] has quit [Quit: Leaving] 07:08 < m-schmoock> cdecker: my wait for remote channel active test fails on travis: https://travis-ci.org/ElementsProject/lightning/jobs/621619683#L1285 07:11 < m-schmoock> I added a test PR. What did I miss, it really must be stupid otherwise im baffled that this issue not covered with tests yet... 07:40 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Ping timeout: 265 seconds] 07:53 -!- jonatack [~jon@82.102.27.163] has joined #c-lightning 08:02 < m-schmoock> cdecker: can you have a quick look at https://github.com/ElementsProject/lightning/pull/3321 I also cant run this locally, not even with higher timout value. 08:03 < m-schmoock> > py.test -v tests/test_misc.py -k test_wait_channel_active 08:57 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 260 seconds] 10:24 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 10:43 < MrHash> ok darosior i've pushed my plugin to https://github.com/MrHash/amqp-relay for review 10:46 < MrHash> darosior: ^ 10:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 11:43 -!- MrHash [~mrhash@host31-54-194-75.range31-54.btcentralplus.com] has quit [Ping timeout: 265 seconds] 11:53 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning 12:06 -!- jonatack [~jon@82.102.27.163] has quit [Ping timeout: 240 seconds] 12:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 12:43 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning 12:46 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 13:10 <@cdecker> I'll see what I can do m-schmoock :-) 13:19 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning [] 13:20 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning 13:22 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Quit: Textual IRC Client: www.textualapp.com] 13:24 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning 13:37 <@cdecker> m-schmoock: I see the problem: `announce_channels` doesn't actually generate the blocks necessary for channels to be gossiped. You need to call user `wait_for_announce=True` to have it generate enough blocks for gossip 13:37 <@cdecker> Sorry for the confusing names :-) 14:10 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Read error: Connection reset by peer] 14:11 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning 14:27 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has quit [Read error: Connection reset by peer] 14:28 -!- dr-orlovsky [~dr-orlovs@194.230.155.171] has joined #c-lightning 15:15 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 15:17 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 15:42 -!- MrHash [~mrhash@host31-54-194-75.range31-54.btcentralplus.com] has joined #c-lightning 15:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 16:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:59 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection] 19:57 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection] 19:58 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 21:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 21:31 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:34 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning [] 21:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 268 seconds] 21:34 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning 21:58 -!- Victor_sueca is now known as Victorsueca --- Log closed Sat Dec 07 00:00:30 2019