--- Log opened Thu Jun 23 00:00:00 2022 00:05 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 240 seconds] 00:14 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)] 00:19 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #c-lightning 01:02 -!- valwal0 [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #c-lightning 01:04 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Ping timeout: 248 seconds] 01:04 -!- valwal0 is now known as valwal 01:09 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)] 01:09 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #c-lightning 01:30 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds] 02:00 -!- mandelbit[m] [~mandelbit@2001:470:69fc:105::2:176b] has quit [Quit: You have been kicked for being idle] 02:04 -!- kexkey [~kexkey@178.249.214.18] has quit [Ping timeout: 248 seconds] 02:06 -!- kexkey [~kexkey@178.249.214.10] has joined #c-lightning 02:44 -!- valwal [~valwal@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #c-lightning 03:09 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has joined #c-lightning 03:22 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 03:48 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has quit [Ping timeout: 240 seconds] 04:17 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has joined #c-lightning 04:33 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has quit [Ping timeout: 240 seconds] 05:34 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has joined #c-lightning 05:52 -!- rusty [~rusty@114-30-98-125.tpgi.com.au] has quit [Ping timeout: 246 seconds] 05:52 < Igor[m]1> A few more untracked files: `.msggen.json`, `cln-grpc` (root dir), `cln-rpc/src/model.rs`. They were probably generated by plugins during make 05:53 < Igor[m]1> Correction: they are modified, not untracked 06:02 < Igor[m]1> Is this section still relevant? Looks like there is no plugin named `helpme`: https://lightning.readthedocs.io/FAQ.html#i-don-t-know-where-to-start-help-me 06:15 < vincenzopalazzo> "Is this section still relevant..." <- there is https://github.com/lightningd/plugins 06:17 < Igor[m]1> Ah, I see. It's not bundled in the main repo 06:18 < vincenzopalazzo> "Correction: they are modified..." <- yeah this is on my todo list, rust is optional, so some PR that came in are not able to build and update the rust model, and this break the stuff. I'm still under the opinion to remove the autogenerate file until we are not put rust are requirements dependecies. However, the fix where I'm working on is a CI check like we do with the docs 06:19 < vincenzopalazzo> Igor[m]1: no, each time that you find "you can use a plugin" is refering to the plugin repo. 06:19 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Ping timeout (120 seconds)] 06:24 < Igor[m]1> "yeah this is on my todo list..." <- Those `.proto` files are supposed to change only with new releases, I guess. I'm using them in my gRPC CL client and committing updates to those files before a new release comes would break a lot of things 06:27 < vincenzopalazzo> Igor[m]1: I don't think so, this need to be changed into each change that effect these file, otherwise you can not test the new feature. I like test in production :) it is alway a bad idea 06:33 < Igor[m]1> "I don't think so, this need to..." <- The problem is, people are encouraged to go to the master branch to get `.proto` mappings: https://medium.com/blockstream/core-lightning-v0-11-0-channel-multiplexing-a-new-api-and-much-more-5d34df8cfeb5 06:38 < Igor[m]1> If those mappings will contain unreleased changes, it will cause a lot of issues 06:46 < Igor[m]1> Since the API can change, maybe it would make sense to have a special dir for each released version's mappings, something like `/grpc/v0.11.0/*.proto`, it would allow API consumers to choose the bindings for the version they are currently targeting 06:46 -!- jespada [~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net] has quit [Ping timeout: 256 seconds] 06:50 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 06:51 -!- jespada [~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net] has joined #c-lightning 06:51 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Client Quit] 07:01 < vincenzopalazzo> "Since the API can change..." <- why not just check out the v.11.0 git tag? 07:27 < Igor[m]1> "why not just check out the v.11...." <- The link in the post points to master, but the actual mappings might not play well with 0.11.0 07:40 < Igor[m]1> * The link in the post points to master, but the actual mappings might not play well with 0.11.0 in case they get updated 07:57 < vincenzopalazzo> "The link in the post points to..." <- Mh! I don't know what post do you mean, BTW I think the docs for the grpc is missing. I had a summer of bitcoin guys that are working on a client, maybe he can help to make some docs too 07:57 < vincenzopalazzo> BTW, I think if you want the grpc v.0.11, you just checkout the git tag version 10:14 -!- belcher [~belcher@user/belcher] has joined #c-lightning 10:18 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 10:51 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Quit: Konversation terminated!] 10:56 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 11:54 -!- jarthur [~jarthur@user/jarthur] has joined #c-lightning 12:14 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 12:26 -!- belcher [~belcher@user/belcher] has quit [Quit: Leaving] 13:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds] 13:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 13:42 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Ping timeout (120 seconds)] 14:08 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds] 14:10 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 14:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds] 14:30 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 15:07 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 268 seconds] 15:37 -!- grubman [~ufotofu@149.248.16.17] has joined #c-lightning 16:37 -!- rusty [~rusty@pa49-178-164-157.pa.nsw.optusnet.com.au] has joined #c-lightning 17:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:20 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 18:59 -!- rusty [~rusty@pa49-178-164-157.pa.nsw.optusnet.com.au] has left #c-lightning [] 19:56 -!- jarthur_ [~jarthur@user/jarthur] has joined #c-lightning 19:58 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 264 seconds] 20:32 -!- zeropoint [~alex@c-67-169-157-130.hsd1.ca.comcast.net] has joined #c-lightning 20:33 -!- zeropoint [~alex@c-67-169-157-130.hsd1.ca.comcast.net] has quit [Client Quit] 21:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection] 21:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning 22:15 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection] 22:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Write error: Connection reset by peer] 22:16 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #c-lightning 22:17 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 22:43 -!- evanlinjin_ [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 268 seconds] --- Log closed Fri Jun 24 00:00:01 2022