Closed Fryuni closed 2 years ago
withtypes
commented
2 years ago I also get the error on Ubuntu 18.04.6 when doing cargo install lunatic but when I install it from a git repo (the same version/release) with cargo install --git https://github.com/lunatic-solutions/lunatic.git --tag v0.9.0 it works.
pinkforest
commented
2 years ago Hey lovelies, I wouldn't mind dig deep into this :rabbit: :hole: .. :carrot:
would you all mind telling what your cc --version , ld --version and rustup show and cargo --version says ?
Cheers
pinkforest
commented
2 years ago The crate version is essentially the .tar:
wget https://crates.io/api/v1/crates/lunatic-runtime/0.9.0/download
git version essentially is:
git clone https://github.com/lunatic-solutions/lunatic.git -b v0.9.0
Cargo.lock is pretty diferent between them... let me see
thaodt
commented
2 years ago hi @pinkforest im experimenting the same issue on Manjaro Linux - kernel version 5.15.55-1-MANJARO. I will provide the details below.
The output of rustup show:
Default host: x86_64-unknown-linux-gnu
rustup home: /home/thaodt/.rustup
installed toolchains
--------------------
stable-x86_64-unknown-linux-gnu (default)
nightly-2020-10-25-x86_64-unknown-linux-gnu
nightly-2021-11-20-x86_64-unknown-linux-gnu
nightly-2021-12-13-x86_64-unknown-linux-gnu
nightly-2022-01-16-x86_64-unknown-linux-gnu
nightly-2022-01-17-x86_64-unknown-linux-gnu
nightly-2022-02-19-x86_64-unknown-linux-gnu
nightly-2022-05-01-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu
1.53-x86_64-unknown-linux-gnu
1.61-x86_64-unknown-linux-gnu
1.40.0-x86_64-unknown-linux-gnu
1.48.0-x86_64-unknown-linux-gnu
1.55.0-x86_64-unknown-linux-gnu
1.56.0-x86_64-unknown-linux-gnu
1.56.1-x86_64-unknown-linux-gnu
1.57.0-x86_64-unknown-linux-gnu
1.58.1-x86_64-unknown-linux-gnu
1.60.0-x86_64-unknown-linux-gnu
1.61.0-x86_64-unknown-linux-gnu
1.62.0-x86_64-unknown-linux-gnu
installed targets for active toolchain
--------------------------------------
aarch64-apple-darwin
aarch64-apple-ios
aarch64-linux-android
armv7-linux-androideabi
i686-linux-android
wasm32-unknown-unknown
wasm32-wasi
x86_64-apple-darwin
x86_64-apple-ios
x86_64-linux-android
x86_64-unknown-linux-gnu
active toolchain
----------------
stable-x86_64-unknown-linux-gnu (default)
rustc 1.62.1 (e092d0b6b 2022-07-16)Output of ld --version:
GNU ld (GNU Binutils) 2.38
Copyright (C) 2022 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.Output of cc --version:
cc (GCC) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.Ok .. @bkolobara is going to push 0.9.1 to Crates.io with the git manifests and that should fix this in this semver so people who follow 0.9 guidance will not get this friction
pinkforest
commented
2 years ago @thaodt can you do rustup default nightly and re-try what led to error ?
Also try rustup default 1.61.0
pinkforest
commented
2 years ago We found out that with 1.62.1 it doesn't work from crates.io.. @bkolobara essentially pushed v0.9.0 git into crates.io as 0.9.1 ...
Now this is getting interesting :popcorn:
pinkforest
commented
2 years ago @bkolobara one could be that git brings all the inter-dependencies in monorepo too.. meaning that if you publish all dependency crates in crates.io you might have forgotten to publish some dependency crate ? let me dig into that.....
pinkforest
commented
2 years ago Hmm the published deps loook fine .. this weirdly only affects 1.62.1
need to dig deeper as 0.9.1 from crates.io resolver is broken even if it's the clone of 0.9.0 git
foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version hash-map-id/Cargo.toml
version = "0.9.0"
foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-common-api/Cargo.toml
version = "0.9.0"
foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-error-api/Cargo.toml
version = "0.9.0"
hash-map-id = { version = "^0.9", path = "../hash-map-id" }
lunatic-common-api = { version = "^0.9", path = "../lunatic-common-api" }foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-messaging-api/Cargo.toml
version = "0.9.0"
async-std = { version = "^1.0", features = ["attributes", "unstable"] }
tokio = { version = "^1.14", features = ["macros"] }
hash-map-id = { version = "^0.9", path = "../hash-map-id" }
lunatic-process = { version = "^0.9", path = "../lunatic-process" }
lunatic-common-api = { version = "^0.9", path = "../lunatic-common-api" }
lunatic-process-api = { version = "^0.9", path = "../lunatic-process-api" }
lunatic-networking-api = { version = "^0.9", path = "../lunatic-networking-api" }foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-networking-api/Cargo.toml
version = "0.9.0"
async-std = { version = "^1.0", features = ["attributes", "unstable"] }
tokio = { version = "^1.14", features = ["macros"] }
hash-map-id = { version = "^0.9", path = "../hash-map-id" }
lunatic-common-api = { version = "^0.9", path = "../lunatic-common-api" }
lunatic-error-api = { version = "^0.9", path = "../lunatic-error-api" }foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-process/Cargo.toml
version = "0.9.0"
uuid = { version = "^0.8", features = ["v4"] }
async-std = { version = "^1.0", features = ["attributes", "unstable"] }
tokio = { version = "^1.14", features = ["macros"] }
hash-map-id = { version = "^0.9", path = "../hash-map-id" }foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-process-api/Cargo.toml
version = "0.9.0"
uuid = { version = "^0.8", features = ["v4"] }
async-std = { version = "^1.0", features = ["attributes", "unstable"] }
hash-map-id = { version = "^0.9", path = "../hash-map-id" }
lunatic-stdout-capture = { version = "^0.9", path = "../lunatic-stdout-capture" }
lunatic-process = { version = "^0.9", path = "../lunatic-process" }
lunatic-common-api = { version = "^0.9", path = "../lunatic-common-api" }
lunatic-error-api = { version = "^0.9", path = "../lunatic-error-api" }
lunatic-wasi-api = { version = "^0.9", path = "../lunatic-wasi-api" }foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-registry-api/Cargo.toml
version = "0.9.0"
hash-map-id = { version = "^0.9", path = "../hash-map-id" }
lunatic-process = { version = "^0.9", path = "../lunatic-process" }
lunatic-process-api = { version = "^0.9", path = "../lunatic-process-api" }
lunatic-common-api = { version = "^0.9", path = "../lunatic-common-api" }foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-stdout-capture/Cargo.toml
version = "0.9.0"
foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-version-api/Cargo.toml
name = "lunatic-version-api"
version = "0.9.0"
description = "Lunatic host functions for getting Lunatic host version"
repository = "https://github.com/lunatic-solutions/lunatic/tree/main/crates/lunatic-version-api"foobar@foobar-MS-7C77:~/gg/lunas/lunatic-git-v0.9.0/crates$ grep version lunatic-wasi-api/Cargo.toml
version = "0.9.0"
async-std = { version = "^1.0", features = ["attributes", "unstable"] }
tokio = { version = "^1.14", features = ["macros"] }
hash-map-id = { version = "^0.9", path = "../hash-map-id" }
lunatic-common-api = { version = "^0.9", path = "../lunatic-common-api" }
lunatic-process = { version = "^0.9", path = "../lunatic-process" }
lunatic-stdout-capture = { version = "^0.9", path = "../lunatic-stdout-capture" }Yeah so current theory is that the in-monorepo deps under crates/ referred to old lockfile
@bkolobara will release 0.9.2 with all deps aligned to 0.9.2 to see if we fix this with 1.62.1 -
The current stable where everyone are atm is broken via crates.io
0.9.2 because anyone using 0.9 manifest would hit this problem with current stable so it is essential to have a working 0.9 semver
pinkforest
commented
2 years ago Okay 0.9.2 now solved this.. thanks @bkolobara - this can be closed - can you retry now @Fryuni and @withtypes ?
first:
rustup default 1.62.1
and then:
$ cargo install lunatic-runtime
Updating crates.io index
Downloaded lunatic-runtime v0.9.2
Downloaded 1 crate (45.3 KB) in 1.31s
Installing lunatic-runtime v0.9.2
..that built fine now
bkolobara
commented
2 years ago Fixed with v0.9.2. I yanked v0.9.0 and v0.9.1.
Just did a fresh install (literally installed rustup and did
cargo install lunatic-runtime) and got this error:Running on a clean Pop OS:
I haven't used wasmtime before lunatic and it does a great job at keeping it hidden away from me so I don't know how to even try to debug this.