--- Log opened Mon May 23 00:00:31 2022 00:45 -!- rusty [~rusty@14-201-152-82.tpgi.com.au] has quit [Ping timeout: 260 seconds] 01:49 -!- mn3monic [~guido@vmi884119.contaboserver.net] has joined #c-lightning 01:57 < mn3monic> Hello. Has anyone been successful on building a container with the CLN original Dockerfile (from the GH repo) in Teamcity CI? 01:58 < vincenzopalazzo> mn3monic: Why docker file are you using? we are different docker file in the github repo 01:59 < mn3monic> hi vincenzo, the one in the root directory 02:01 < mn3monic> but now that you tell me, I'm going to try with the dockerfiles in contrib :p 02:01 < vincenzopalazzo> Mh it should be the correct one, can you report also the error that you had? 02:01 < vincenzopalazzo> mn3monic: depends what you need to do :) 02:02 < mn3monic> about reporting, sure, let me upload a couple of screenshot and I'm done 02:02 -!- kexkey [~kexkey@178.249.214.19] has quit [Ping timeout: 246 seconds] 02:03 < mn3monic> I have uploaded them here: https://postimg.cc/gallery/3ThzLWb 02:04 < mn3monic> in one you can see how I configure the CI, I wanted to hook it to /refs/tags/v0.11.1 02:04 < mn3monic> and then there's the build log, in which something is going bad with git 02:05 < mn3monic> I'm quite new with all that teamcity stuff and I don't know how it check outs the sources into the agent containers, actually 02:05 -!- kexkey [~kexkey@178.249.214.10] has joined #c-lightning 02:06 < vincenzopalazzo> mn3monic: same here, I never had the opportunity to play with it 02:08 < vincenzopalazzo> the error looks like to git https://stackoverflow.com/a/6268528/10854225 02:11 < vincenzopalazzo> maybe cdecker solve this issue with pypi? or maybe I remember wrong 02:12 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 02:25 < mn3monic> vincenzopalazzo, however the build failed with the alpine docker file (lack of git according the build lock) but has been successful with Dockerfile.ubuntu and I have now clightning in my private registry built from blockstream repository 02:26 < mn3monic> which is quite an achievement, thanks for putting me on the right path =) 02:26 < mn3monic> s/build lock/build log 02:36 < mn3monic> ah, no :P 02:36 < mn3monic> the ubuntu container tricked me ahah, the build procedure is in the entry point :D 02:39 < vincenzopalazzo> ops! yeah this is my fault sorry! it is used only to run lnprototest 02:42 < mn3monic> I see, nm =) 02:42 < mn3monic> let me look if I can prune that origins after checking out the sources into the CI agents 02:48 < vincenzopalazzo> Maybe you can have an hack in the checkout with a diff patch and apply during the CI workflow? not sure but sometimes this works for me 02:59 -!- mn3monic [~guido@vmi884119.contaboserver.net] has quit [Ping timeout: 255 seconds] 03:03 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 03:04 -!- mn3monic [~guido@net-5-94-10-88.cust.vodafonedsl.it] has joined #c-lightning 03:42 < mn3monic> vincenzopalazzo I worked around the issue by modifying the Dockerfile and hosting it on my own repo. With no sources, my Dockerfile avoids the copy part, clone the sources from the ElementsProject repo and check out to v0.11.1 right after. I'd love to avoid that but it's ok anyway, something strange inside the TeamCity containers agent is happening while checking out the sources. it's even not reproducible outside the agent's cont 03:42 < mn3monic> ainers 03:45 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 03:56 -!- litch [~litch@2605:a601:aa3d:3a00:c002:ce4f:7c7:a541] has quit [Remote host closed the connection] 03:57 -!- litch [~litch@2605:a601:aa3d:3a00:c002:ce4f:7c7:a541] has joined #c-lightning 04:16 -!- rusty [~rusty@14-201-152-82.tpgi.com.au] has joined #c-lightning 04:22 -!- rusty [~rusty@14-201-152-82.tpgi.com.au] has quit [Ping timeout: 255 seconds] 04:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 05:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:44 -!- litch [~litch@2605:a601:aa3d:3a00:c002:ce4f:7c7:a541] has quit [Ping timeout: 244 seconds] 05:51 -!- litch [~litch@2605:a601:aa3d:3a00:9805:a6fa:696f:7c9a] has joined #c-lightning 05:53 -!- litch_ [~litch@2605:a601:aa3d:3a00:e5e7:e3b:3c6d:b5c5] has joined #c-lightning 05:56 -!- litch [~litch@2605:a601:aa3d:3a00:9805:a6fa:696f:7c9a] has quit [Ping timeout: 255 seconds] 06:41 -!- litch_ [~litch@2605:a601:aa3d:3a00:e5e7:e3b:3c6d:b5c5] has quit [Remote host closed the connection] 07:17 -!- mandelbit[m] [~mandelbit@2001:470:69fc:105::2:176b] has joined #c-lightning 07:46 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Remote host closed the connection] 07:46 -!- befalou [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 07:47 -!- litch [~litch@2600:380:9b2a:f551:3c03:37:9d45:b142] has joined #c-lightning 07:54 -!- litch [~litch@2600:380:9b2a:f551:3c03:37:9d45:b142] has quit [] 08:02 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Ping timeout: 240 seconds] 08:55 -!- befalou [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 09:25 -!- Guest41 [~Guest41@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has joined #c-lightning 09:26 < Guest41> Hi everyone. I have a question about the "lightning-cli". I want to query for a specific invoice by payment_hash. It doesn't seem to work when I try: 09:26 < Guest41> lightning-cli --rpc-file /root/.lightning/lightning-rpc listinvoices 2bda9a1cad9295d746d498f63f22d0f523ce99a5cd6c1e1e6460767c1b789744 09:27 < Guest41> am I specifying the payment hash correctly? 09:28 < Guest41> I get an empty result list as a result: 09:28 < Guest41> root@373ed858cd74:/# lightning-cli --rpc-file /root/.lightning/lightning-rpc listinvoices 2bda9a1cad9295d746d498f63f22d0f523ce99a5cd6c1e1e6460767c1b789744 09:28 < Guest41> { 09:28 < Guest41>    "invoices": [] 09:28 < Guest41> } 09:29 < vincenzopalazzo> listinvoices payment_hash={} 09:29 < vincenzopalazzo> without key lighitning-cli follow the doc order https://lightning.readthedocs.io/lightning-listinvoices.7.html 09:30 < Guest41> yes, I am trying to follow that doc 09:31 < vincenzopalazzo> this works `listinvoices payment_hash={}` 09:33 < Guest41> can you give an example of a full command with a specific payment hash. I get an error: 09:33 < Guest41> lightning-cli --rpc-file /root/.lightning/lightning-rpc listinvoices payment_hash={"2bda9a1cad9295d746d498f63f22d0f523ce99a5cd6c1e1e6460767c1b789744"} 09:33 < Guest41> lightning-cli: Some parameters are malformed, cannot create a valid JSON-RPC request: { "jsonrpc" : "2.0", "method" : "listinvoices", "id" : "lightning-cli-2091", "params" :{ "payment_hash" : {2bda9a1cad9295d746d498f63f22d0f523ce99a5cd6c1e1e6460767c1b789744}} } 09:34 < vincenzopalazzo> `listinvoices payment_hash=2bda9a1cad9295d746d498f63f22d0f523ce99a5cd6c1e1e6460767c1b789744` 09:34 < Guest41> thanks! 09:35 < Guest41> actually I am trying to use the Rust library to call this RPC: 09:35 < Guest41> https://github.com/laanwj/rust-clightning-rpc/blob/92912c8a5318624b2c9684676a0f697b4a38432e/rpc/src/lightningrpc.rs#L115-L118 09:35 < vincenzopalazzo> ok I'm the mantainer of this lib 09:35 < Guest41> do you know how I can specify this same RPC call as a rust method call? 09:35 < Guest41> perfect! 09:36 < vincenzopalazzo> I need to release the crater of the new version, because I'm splitting this in more craters to make a dep free rust lib 09:37 < vincenzopalazzo> You can use the following generic method to call the API of core lightning https://github.com/laanwj/rust-clightning-rpc/blob/master/common/examples/lowlevel_1.rs 09:37 < Guest41> so this would be the workaround to use for now until you publish the new version of the library? 09:38 < vincenzopalazzo> but for the moment you need to https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories 09:38 < vincenzopalazzo> Guest41: this are the new API of the crater, and I will make the change also in the API that you are mensioning 09:39 < vincenzopalazzo> However, there is an official package of rust that maybe can help you right now without workaround 09:39 < vincenzopalazzo> https://github.com/ElementsProject/lightning/tree/master/cln-rpc 09:39 < vincenzopalazzo> but you need to use tokio 09:41 < Guest41> so i have two options: 09:41 < Guest41> 1) use clightningrpc with the workaround 09:41 < Guest41> 2) use cln-rpc 09:41 < Guest41> is that right? 09:43 < vincenzopalazzo> yep! if you have already started to work with clightningrpc or you have usign another async runing from tokio I can try to publish the crate in beta by today! so more test can be good 09:44 < Guest41> i have already started working with clightningrpc for the rest of the project, so I will try the workaround 09:44 < Guest41> actually I have another question. Will clightningrpc support async methods in the future 09:46 < vincenzopalazzo> when I will came up with a good design yes! the problem of async with rust is that you are coupled with a runtime, so tokio in an embedded device is not so good, or if you want to include a dep with another runtime you can't! 09:47 < vincenzopalazzo> if you are using tokio, I think that cln-rpc is the way to go! i will not make the same work if there is already another crater that do the same job. clightningrpc point to have a different design from cln-rpc 09:48 < Guest41> I see. I am using tokio in my project, so maybe I'll try using cln-rpc 09:49 < vincenzopalazzo> it is the way to go 09:49 < Guest41> thanks (y) 10:01 -!- befalou_ [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 10:03 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Ping timeout: 240 seconds] 10:21 -!- Guest41 [~Guest41@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has quit [Quit: Ping timeout (120 seconds)] 10:46 -!- csknk [~csknk@88.87.164.26] has joined #c-lightning 12:13 -!- csknk [~csknk@88.87.164.26] has quit [Quit: leaving] 12:34 -!- rusty [~rusty@14-201-152-82.tpgi.com.au] has joined #c-lightning 14:41 -!- rusty [~rusty@14-201-152-82.tpgi.com.au] has quit [Ping timeout: 246 seconds] 14:59 -!- befalou_ is now known as befalou 15:25 -!- befalou_ [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 15:27 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Remote host closed the connection] 15:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 16:14 -!- rusty [~rusty@tro1759202.lnk.telstra.net] has joined #c-lightning 16:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 16:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 16:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 16:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 16:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 16:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 17:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:27 -!- rusty [~rusty@tro1759202.lnk.telstra.net] has quit [Ping timeout: 246 seconds] 17:50 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning 19:36 -!- sr_gi[m] [~srgimatri@2001:470:69fc:105::1:c14c] has quit [Ping timeout: 240 seconds] 19:51 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 258 seconds] 19:52 -!- sr_gi[m] [~srgimatri@2001:470:69fc:105::1:c14c] has joined #c-lightning 20:04 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning 21:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 21:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 22:38 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 244 seconds] 23:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 23:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning --- Log closed Tue May 24 00:00:32 2022