search

paritytech / substrate-contracts-node

Minimal Substrate node configured for smart contracts via pallet-contracts.
The Unlicense
123 stars 140 forks source link

Is estuary dependency required in v0.40.0? #231

Open ltfschoen opened 5 months ago

ltfschoen commented 5 months ago

In previous versions we needed to use estuary as a lightweight cargo registry in the CI to test if publishing cargo-contract to it and installing it from there works by running cargo install --git https://github.com/onelson/estuary.git --force

Do we still need to run that as shown here https://github.com/ltfschoen/XCMTemplate/blob/main/docker/run.sh#L110, because i get the following error with the latest substrate-contracts-node 0.40.0.

echo substrate-contracts-node 0.40.0-17065f31ac4

   Compiling heck v0.3.3
error[E0433]: failed to resolve: could not find `memmem` in `memchr`
   --> /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/pest-2.7.9/src/position.rs:303:33
    |
303 |                         memchr::memmem::find(&self.input.as_bytes()[self.pos..], s1.as_bytes())
    |                                 ^^^^^^ could not find `memmem` in `memchr`

   Compiling textwrap v0.11.0
For more information about this error, try `rustc --explain E0433`.
error: could not compile `pest` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `estuary v0.1.1 (https://github.com/onelson/estuary.git#570d3a8b)`, intermediate artifacts can be found at `/tmp/cargo-install8MZovz`.
smiasojed commented 5 months ago

Hi @ltfschoen, could you please explain the context? It seems like a compilation issue with the estuary crate. Could you point me to the requirement you are referring to? How is it related to substrate-contracts-node?