-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error[E0583]: file not found for module target_chain
#4448
Comments
The file exists, ensure that your git checkout is valid. |
so the way i checked that my git checkout was valid was to run the following: check latest local commit
which output check latest upstream commit
which output i also tried removing the target folder i also changed to i also updated it to use the latest Rust nightly but despite all that i still got the error. I've provided all the code that I'm using here #4450 I'm using Docker Desktop for Mac 4.22.0 (117440) |
i tried doing a fresh clone of the polkadot-sdk of commit 594c3ed5750bc7ab97f82fb8387f82661eca1cc4
then only copied the changes that i made in this PR #4450 to the following files:
and then lastly ran the script
but it gave the same error after 45 mins
|
update: i get that error with the latest polkadot-sdk commit even when i use latest Rust stable (same as with latest Nightly) in this commit bc8c9eb |
i was able to bypass the error by only building the so i need to find out which of these other packages is the one that is causing that error
|
@bkchr so i went through each package, and the only package that triggers the error whereas if i just clone https://github.com/paritytech/polkadot-sdk, and install relevant dependencies and |
Did you ensure that it copied the files correctly? |
i think i'll try doing something like this https://stackoverflow.com/questions/545387/linux-compute-a-single-hash-for-a-given-folder-contents for the folder mentioned. |
so since the issue is in the ./bridges folder,
and then i modified the ./substrate/docker/substrate_builder.Dockerfile so its content was
which output
so although it shows different hashes, the original so i installed
and then ran
and then i modified the ./substrate/docker/substrate_builder.Dockerfile so its content was
which output the following when i ran
so i can't see any matching hash then i tried doing the same for another random folder ./cumulus on host machine macOS 14.1.1
and then i modified the ./substrate/docker/substrate_builder.Dockerfile so its content was
which output the following when i ran
so even the hash of that folder doesn't match so i just created a random folder and file and then i modified the ./substrate/docker/substrate_builder.Dockerfile so its content was
and that output
and even that doesn't match. so i'm not sure if i'm not sure if it's because i'm using tar 1.35 on the host machine macOS vs tar 1.34 in the Docker container linux, or due to some discrepency like mentioned here https://crypto.stackexchange.com/a/72300, or some other reason @bkchr |
i just noticed this other open issue #582, i'm going to see if that encounters the same issue when running |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
Steps to reproduce
build with the following using
RUST_NIGHTLY=2024-04-29
or even the latest Rust version and it generates the errorThe text was updated successfully, but these errors were encountered: