--- Log opened Sun May 09 00:00:49 2021
01:33 -!- frix [~frix@196.50.101.2] has joined #lnp-bp
01:34 < frix> Good day, I wonder if somebody could give me a tip on compiling farcaster-node (-core). It has a dependency on descriptor-wallet. If I build descriptor-wallet stand alone, it builds fine. If it builds via farcaster-project it gives a type error:
01:35 < frix> descriptor-wallet/src/address.rs:117:5
01:35 < frix> StrictDecode
01:35 < frix> ^^^^^^^^^^^^ expected struct `std::string::String`, found `&str`
01:36 < frix> I've updated the cargo file to point to my own downloaded copy of descriptor-wallet (which builds fine by itself) but yet it will not compile against it, giving the same error.
01:36 < frix> I'm running cargo 1.46.0 on Kubuntu 20.04
01:42 < frix> If this is not the correct channel to discuss 'https://github.com/farcaster-project/farcaster-node', can you please point me to another channel?
01:49 < frix> In Cargo.toml of farcaster-core, I override the crates-io to point to the copy of descriptor-wallet that I've downloaded:
01:49 < frix> [patch.crates-io]
01:49 < frix> descriptor-wallet = { path = "~/farcaster/deps/descriptor-wallet" }
01:50 < frix> If I run 'cargo build' inside descriptor-wallet, it compiles correctly and create src/lib.rs
01:50 < frix> If I build via desciptor-wallet, the type errors mentioned above occur...
03:06 < frix> the dependency on descriptor-wallet appears to be from lightning/lnp-core and  rust-internet2/addr, which on their own depends on descriptor-wallet 0.4.0, but the farcaster-core graph ponts to descriptor-wallet 0.4.1
03:08 < dr-orlovsky> Hi Frix! Thanks for reporting. While we can't help with farcaster-project/node, we clearly can help with descriptor-wallet dependency. I will investigate your issue
03:09 < dr-orlovsky> also zkao: is here and he is the author of the farcaster-project, so he may also help or include the solution which we will find into the next release
03:15 < dr-orlovsky> frix: I see now, the problem caused by the recent update in strict_encoding_derive upstream dependency. Working on a fix, will take an hr or so
03:27 < dr-orlovsky> ok, I think I have fix. I need to publish updated version of strict_encoding crate and then you will have to run `cargo update` on your repo. You will not need a forked descriptor wallet code anymore. I will let you known once the update will be published so you can try it
03:46 < frix> hi
03:46 < frix> thank you 1000x for the reply
03:48 < frix> There is also a dependency problem in farcaster-core/chains/Cargo.toml  -- monero = { git = "https://github.com/monero-rs/monero-rs", features = ["strict_encoding_support"]  -- manually downloading monero 11.2 and pointing to that path (monero = { path = "../../deps/monero-rs-0.11.2" })  resolved that problem. I assume they're related to your solution?
03:50 < frix> Git appears to want to pull monero-rs master branch, but the repo only has 'main':
03:51 < frix> Updating git repository `https://github.com/monero-rs/monero-rs` error: failed to get `monero` as a dependency of package `farcaster_chains v0.1.0 (/opt/coin/farcaster/farcaster-core/chains)`
03:51 < frix> Caused by:   failed to load source for dependency `monero` Caused by:  Unable to update https://github.com/monero-rs/monero-rs Caused by:  failed to find branch `master`
03:52 < dr-orlovsky> this seems to be unrelated and potentially caused by the fact that monero-rs team has renamed their branch. We need to ask zkao to fix the line in farcaster-core Cargo.toml such that it will point to the correct branch name
03:59 < frix> chains/Cargo.toml:21 Need to add:   , branch="main" }  (which is 0.12.0 or possibly refer to an earlier version)
04:40 < dr-orlovsky> correct
06:51 < dr-orlovsky> frix: I am working on finalization of the new version, have to do more test coverage, will take probably till the evening
07:55 < frix> No problem. Thank you for the reply
08:27 < dr-orlovsky> frix: can you pls try `cargo update` now? The system should compile
08:28 < dr-orlovsky> I have released strict_encoding crate v1.3.0 which is compatible with strict_encoding_derive 1.1.0 and should be picked by cargo update
09:55 < frix> dr-orlivsky: I've done a "cargo clean ; cargo update ; cargo build --all-features" in farccaster-core
09:56 < frix> I could see the cargo package update:   Updating strict_encoding v1.2.3 -> v1.3.0
09:56 < frix> Upon building I got another error referring to strict_encoding:
09:56 < frix> core/src/crypto.rs:59:3  #[strict_encoding_crate(strict_encoding)]  help: a derive helper attribute with a similar name exists: `strict_encoding`
09:57 < frix> Same error at: core/src/crypto.rs:111, core/src/datum.rs:16, core/src/protocol_message.rs:21, ... for a total of 11 similar errors
09:59 < frix> If I perform the build inside farcaster-node it has a build error on lnpbp v0.4.0 package: Compiling lnpbp v0.4.0 error[E0432]: unresolved imports `strict_encoding::impl_enum_strict_encoding`, `strict_encoding::test_encode`, `strict_encoding::test_enum_u8_exhaustive`, `strict_encoding::test_garbage_exhaustive`
10:00 < frix> in lnpbp-0.4.0/src/lib.rs:49 and :50
10:51 < frix> just a heads up - I'm running ubuntu 20.04 with rustc v 1.47 -- It seems that a compiler error that I'm getting regarding "use of unstable library feature 'bool_to_option'" was resolved in rustc 1.50.  The dependency hell is starting to heat up again
11:26 -!- frix [~frix@196.50.101.2] has quit [Remote host closed the connection]
11:46 -!- frix [~frix@196.50.101.2] has joined #lnp-bp
14:23 -!- frix [~frix@196.50.101.2] has quit [Quit: Konversation terminated!]
14:23 -!- frix [~frix@196.50.101.2] has joined #lnp-bp
14:37 -!- frix [~frix@196.50.101.2] has quit [Quit: Konversation terminated!]
15:23 < zkao> ops, frix is gone, sorry for the farcaster troubleshooting in here, our channel is #monero-swap
--- Log closed Mon May 10 00:00:51 2021