error: could not compile `smoldot` (lib) about rust HOT 9 CLOSED

El problema no está en el paquete smoldot. Es algo relacionado con el uso de nvm y el modo estricto. Sea como sea, se resuelve o se rompe dependiendo del espacio de trabajo.
Unos hablan de quitar strict mode y otros lo resuelven dejando de usar pnpm temporalmente hasta que se resuelva. Estoy trabajando en polkadot y en astar. En uno de los dos casos o en ambos, se dificulta el acceso a interactuar contractualmente con rust. Realmente sé igual de poco de rust que de solidity. Elegiré mi camino, pero el día que tenga dinero no tendré un ubuntu. Tendré un ubunrtu PRO y una capsula espacial.

from rust.

I cannot reproduce this ICE just through the given command (RUST_BACKTRACE=full cargo install contracts-node), thus some kind of local state seems to be involved. As the comment (in spanish, I translated it using google) says, it doesn't seem to originate in the crate itself. Recently I've had some ICEs from corrupted up target/ directories? Though there is some obligation failing in trait selection which is a bit suspicious (based on the trace, around here.

I tested this on:

jonathan@kili ~ % rustc --version --verbose
rustc 1.77.2 (25ef9e3d8 2024-04-09)
binary: rustc
commit-hash: 25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04
commit-date: 2024-04-09
host: x86_64-unknown-linux-gnu
release: 1.77.2
LLVM version: 17.0.6

As @asggWa seems to be using Ubuntu, I tried the same on rustc 1.75 (as the rust package on ubuntu is version 1.75). However, I still cannot reproduce.

@asggWa Could you tell us which version of rust you used?

from rust.

Possibly it is rustc that is out of range. I'll try uploading rustc, which is what I can do.

rustc 1.69.0 (84c898d 2023-04-16)
binary: rustc
commit-hash: 84c898d
commit-date: 2023-04-16
host: x86_64-unknown-linux-gnu
release: 1.69.0
LLVM version: 15.0.7

from rust.

Possibly the problem now appears again in another stage of the site; but in my case I solved it because I saw that you were using a more current version than mine and other users solved it by reinstalling. My problem now is that it is slow, and the problem is that it arrives. Thank you so much @jdonszelmann .

from rust.

No problem

from rust.

I tested RUST_BACKTRACE=full cargo install contracts-node on 1.69 and I can compile to as far as smoldot (it doesn't ICE) but later on I get an MSRV error, one of the other libraries needs 1.70 minimum:

vice` at 7.0 MB)
error: failed to compile `contracts-node v0.40.0`, intermediate artifacts can be found at `/tmp/cargo-installyotLUh`

Caused by:
  package `polkavm-linux-raw v0.9.0` cannot be built because it requires rustc 1.70.0 or newer, while the currently active rustc version is1.69.0
  Try re-running cargo install with `--locked`
RUST_BACKTRACE=full cargo +1.69.0 install contracts-node  65.99s user4.48s system 86% cpu 1:21.02 total

(so still cannot reproduce unfortunately)

from rust.

msrv seems to be 1.74.1, on which the ICE does not happen on its own. So there must be something else in the build environment of @asggWa that causes it.

from rust.

I'm kinda new to the triage process, but I'm guessing this is a good candidate for S-needs-repro?

@rustbot label +S-needs-repro

from rust.

Now my previous problem is solved and I'm just looking for a way for someone to reproduce the problem. I want to host an application on astar and one of the main obstacles is that I do not want to fill out the form without having a domain name. treebtc.astar.network tree.btc.astar or simply https://treebtc/index.html the idea is not to have a name that hits because it is a local development environment and with the twelve euros they want for the domain I will buy twelve sausage sandwiches maximum when in three days the telephone people find out that I need a static IP so I don't have to go back to the host file to configure and I change it and then I need that, Windows, Mac, a Coca-Cola and a Docker instance on the cloud.
You may need that. A space capsule with certificate and earpieces.

from rust.