--- Log opened Sat Aug 07 00:00:31 2021 00:06 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 01:02 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 01:24 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds] 01:31 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 08:42 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 244 seconds] 09:20 -!- aechu [~major@gateway/tor-sasl/major] has quit [Ping timeout: 244 seconds] 09:27 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning 09:29 -!- early [~early@static.38.6.217.95.clients.your-server.de] has quit [Quit: Leaving] 09:36 -!- early [~early@static.38.6.217.95.clients.your-server.de] has joined #c-lightning 09:39 -!- early [~early@static.38.6.217.95.clients.your-server.de] has quit [Client Quit] 09:42 -!- early [~early@static.38.6.217.95.clients.your-server.de] has joined #c-lightning 11:52 -!- belcher_ is now known as belcher 12:56 < ufotofu> hm running into the bug where you can't open a channel with confirmed outputs 12:56 < ufotofu> i think fiatjaf mentioned this in the telegram group 12:57 < ufotofu> "message": "Could not afford all using all 0 available UTXOs: all short" 12:57 < ufotofu> but the output shows 12:57 < ufotofu> "status": "confirmed", 13:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 244 seconds] 13:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 13:35 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 258 seconds] 13:36 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 13:37 -!- Shing [~Shing@45.131.194.35] has joined #c-lightning 13:40 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Read error: No route to host] 14:30 -!- DeanGuss [~dean@user/deanguss] has quit [Quit: buhbye] 14:58 -!- DeanGuss [~dean@nonplayercharacter.me] has joined #c-lightning 14:58 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host] 14:58 -!- DeanGuss [~dean@user/deanguss] has joined #c-lightning 15:12 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 15:42 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning 15:42 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 258 seconds] 17:19 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds] 18:36 -!- jarthur_ [~jarthur@2603-8080-1540-002d-f9c9-12c1-1bdd-7dd0.res6.spectrum.com] has joined #c-lightning 18:40 -!- jarthur [~jarthur@2603-8080-1540-002d-dd8f-ae40-8c90-f67d.res6.spectrum.com] has quit [Ping timeout: 252 seconds] 18:41 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 19:01 -!- jarthur_ [~jarthur@2603-8080-1540-002d-f9c9-12c1-1bdd-7dd0.res6.spectrum.com] has quit [Quit: jarthur_] 20:25 < Shing> hi yall, i'm working on this issue: https://github.com/ElementsProject/lightning/issues/3662. I see some methods that stub these notify_* methods. It doesnt seem like i need to write individual tests for my new notificaiton since i don't see any for the other ones; what should i use as the baseline testing benchmark before i create a PR? Thanks! 20:27 < Shing> this is my first PR for this project and open source in general, so i apologize if these are annoying newbie questions 21:16 < rusty> Shing: Hi! Most of the notification tests are done by writing a new plugin in tests/plugins/ and loading from a (new) test in tests/test_plugin.py 21:22 < Shing> rusty gotcha, i'll go take a look! 21:35 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 245 seconds] 21:53 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 22:35 < Shing> is there a way to run the tests without needing bitcoind? 23:01 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 240 seconds] 23:56 -!- belcher_ is now known as belcher --- Log closed Sun Aug 08 00:00:32 2021