--- Log opened Mon Jan 31 00:00:45 2022 00:13 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 00:36 -!- cdecker[m] [~cdeckerma@2001:470:69fc:105::2e8e] has quit [Ping timeout: 268 seconds] 00:39 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 256 seconds] 00:40 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning 00:40 -!- cdecker[m] [~cdeckerma@2001:470:69fc:105::2e8e] has joined #c-lightning 01:00 -!- vincenzopalazzo [~vincenzop@2001:470:69fc:105::a67] has joined #c-lightning 01:00 < vincenzopalazzo> cdecker: I'm reviewing the #5010 and in the code generation there is a part where in the serde alias are set also the [], I'm missing some things in serde that I don't know or it is a bug in the code-gen? https://github.com/ElementsProject/lightning/pull/5010/files#diff-8856fabd31dcd921e0f473064cc45fb06d6f6d756520c7628b6e2d6b6bbb798dR189 01:03 < cdecker[m]> Yeah, I need to trim those `[]` but have been working in other things over the weekend. That being said it's pretty trivial, since it's an alias, i.e., "if you don't find an exact match please also look for the alias" which never happens in our case so far (it'd happen when we have spaces or dashes in array names). 01:13 < vincenzopalazzo> cdecker: Yep, I'm driven into it :) I just asking because I would not say somethings wrong and lose your time :) 01:52 < michaelfolkson> What's the thinking behind which plugins make it to the "Available plugins" list on the README? Is there any thinking? Just plugins that are surfaced to the user (not plugins like datastore that other plugins make use of in the background)? 01:52 -!- kakolainen[m] [~kakolaine@2001:470:69fc:105::34f9] has joined #c-lightning 01:52 -!- devrandom [~devrandom@2001:470:69fc:105::d4d] has joined #c-lightning 01:53 < michaelfolkson> https://github.com/lightningd/plugins#available-plugins 01:54 < michaelfolkson> It might just not have been updated in a while. Missing others like the historian plugin etc 02:03 -!- kexkey [~kexkey@static-198-54-132-122.cust.tzulo.com] has quit [Ping timeout: 250 seconds] 02:04 -!- kexkey [~kexkey@static-198-54-132-122.cust.tzulo.com] has joined #c-lightning 02:11 < michaelfolkson> Should CLBOSS be added to the available plugins? :0 02:54 -!- willcl_ark [~willcl-ar@2001:470:69fc:105::1:620a] has quit [Changing host] 02:54 -!- willcl_ark [~willcl-ar@user/willcl-ark/x-8282106] has joined #c-lightning 03:18 < michaelfolkson> Transcript from last week's c-lightning call: https://github.com/michaelfolkson/bitcointranscripts/blob/c-lightning-2022-01-24/c-lightning/2022-01-24-developer-call.md 04:00 < cdecker[m]> "Should CLBOSS be added to the..." <- Good idea, we should really build some tooling around that repo and finally get working on a plugin manager client-side to make installing/removing/updating plugins easier 04:36 < michaelfolkson> cdecker[m]: The latter would be finishing the Reckless plugin? 04:37 < michaelfolkson> CLBOSS could interfere with the operation of other plugins I'm guessing 04:40 < michaelfolkson> Some warnings "Don't use CLBOSS with these other plugins" if that's the case 04:46 < darosior> Ideally conflicts would be handled by the plugin manager 04:47 < cdecker[m]> Yeah, conflicts are a bit hard to identify, so we'd likely have to crowdsource them 05:05 < vincenzopalazzo> we should be add some requirements to the plugin developer, like develop a manifest where we can declare the metadata and the plugin manager will check this metadata and give feedback to the user 05:11 < cdecker[m]> A lot of that metadata is already in the manifest message sent to lightningd at startup (hooks, notifications, subscriptions, methods and options) that'd be an easy source for that info. 05:15 < vincenzopalazzo> I see, but with a manifest for the plugin manager we can detect also language version mismatch, compiler requirements, and mismatch version with c-lightning it self, right? 05:34 < cdecker[m]> Well, hooks and notifications can inform which lightningd version is needed (but may not be sufficient) but runtime environment is out of scope for getmanifest, so yeah we'd need an explicit manifest alongside, though we can likely infer quite a bit 05:40 -!- jespada [~jespada@87.74.36.188] has quit [Ping timeout: 250 seconds] 05:41 < darosior> vincenzopalazzo: if you are interested in taking this over, i can share with you (if others here agree) some discussions we've had around what was needed for integrating reckless (https://github.com/darosior/reckless) in C-lightning and adapting lightningd/plugins to its needs. 05:41 -!- jespada [~jespada@87.74.36.188] has joined #c-lightning 05:52 < vincenzopalazzo> darosior: Sounds good to me, I have some idea also in a package manager for plugins, but for now mine are only ideas that need to be tested by start to coding. But is this problem it is already started to be studied, I would like to jump in if it is possible. Not sure if my time it is enough right time, but for the near future yes I'm interested 05:56 < michaelfolkson> darosior: If you can share more widely please do, I'd be interested to read too 09:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds] 09:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 10:49 -!- rusty [~rusty@203.214.146.158] has joined #c-lightning 11:52 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has joined #c-lightning 14:38 -!- DeanGuss [~dean@user/deanguss] has quit [Ping timeout: 252 seconds] 14:39 -!- DeanGuss [~dean@nonplayercharacter.me] has joined #c-lightning 14:39 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host] 14:39 -!- DeanGuss [~dean@user/deanguss] has joined #c-lightning 15:41 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 256 seconds] 15:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds] 15:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 16:10 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds] 16:11 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 20:33 -!- rusty [~rusty@203.214.146.158] has quit [Ping timeout: 256 seconds] 21:19 -!- rusty [~rusty@203.214.146.158] has joined #c-lightning 22:22 -!- Victorsueca [~Victorsue@user/victorsueca] has quit [Ping timeout: 250 seconds] 22:39 -!- rusty [~rusty@203.214.146.158] has quit [Ping timeout: 256 seconds] --- Log closed Tue Feb 01 00:00:46 2022