Ralph (Aug 06 2024 at 15:47): Ralph (Aug 06 2024 at 15:47):Hey all, I'm using cargo component v0.15.0, and I can't seem to tell it to ignore the registry setting. My commands for a basic usage:
wkg oci pull ghcr.io/webassembly/wasi/http:0.2.0wasm-tools component wit webassembly_wasi_http.wasm --out-dir witcargo component new --proxy hello-wasi-http --lib -t wasi:http/proxy Ralph (Aug 06 2024 at 15:47):now, with the last command I receive the following:
Ralph (Aug 06 2024 at 15:47):error: a default component registry has not been set
Ralph (Aug 06 2024 at 15:51):the help doesn't really specify whether registry means the registry you'll pull from (the future embedded usage of wkg for exmaple) or where I'm going to PUSH the resulting component. So I look in the repo (https://github.com/bytecodealliance/cargo-component/blob/main/docs/design/registries.md) it says, "The registry field is optional and defaults to default (see the [package.metadata.component.registries] table below).`
Ralph (Aug 06 2024 at 15:51):there's an extensive discussion below, but if I'm going to specify --registry is this supposed to be pointing at ghcr.io/webassembly/wasi/http:0.2.0 ????
Ralph (Aug 06 2024 at 15:52):trying to tie the current implementation together with a straightforward workflow.
Taylor Thomas (Aug 06 2024 at 19:03):@Ralph Yeah this is still a work in progress. We are close to getting done with adding pulling from a registry: https://github.com/bytecodealliance/cargo-component/pull/322
There will still be some follow ups after that but we're getting there
Bailey Hayes (Aug 07 2024 at 01:50):Our goal is to have a mirror setup from wasi.dev pointing to ghcr.io/webassembly/wasi packages.
While the OCI workflow is baking, you can set packages like: https://github.com/sunfishcode/hello-wasi-http/blob/main/Cargo.toml#L20-L27. A while back it changed from using a wit dir to this syntax.
Ralph (Aug 07 2024 at 09:19):OK, so I still have a problem and would love to walk it through with someone if they have ten minutes
Ralph (Aug 07 2024 at 09:19):I do cargo component new --lib --proxy hello-wasi-http and that gets me a simple buildable version of hello but that is NOT wasi components yet.
Ralph (Aug 07 2024 at 09:21):so I then download the oci package, and use wasm-tools to generate a directory that comes out like this, flatter than before and in Dan's example: https://github.com/squillace/ralph-messed-up/tree/main/wit.
Ralph (Aug 07 2024 at 09:21):note there's no directory for wit/deps/clocks in this format, so I either have to munge the dir OR I can modify the paths in toml, right?
Ralph (Aug 07 2024 at 09:22):the following paths clearly should NOT work in this environment:
Ralph (Aug 07 2024 at 09:22):[package.metadata.component.dependencies]
"wasi:clocks" = { path = "wit/deps/clocks" }
"wasi:io" = { path = "wit/deps/io" }
"wasi:random" = { path = "wit/deps/random" }
"wasi:cli" = { path = "wit/deps/cli" }
Ralph (Aug 07 2024 at 09:23):so I go to munge the wit into something that looks like dan's:
Ralph (Aug 07 2024 at 09:23):no go
Ralph (Aug 07 2024 at 09:23):cargo component build version 0.15.0 and 0.14.0 do not locate the files so far as I can see.
Ralph (Aug 07 2024 at 09:24):so if this SHOULD work, and it should, then there's something wrong with my machine (entirely possible, detritus is a thing) and I'd like to figure that out.
Ralph (Aug 07 2024 at 09:36):cargo 1.80.0 (376290515 2024-07-16)
cargo-component-component 0.14.0 (wasi:95fee6f) or cargo-component-component 0.15.0 (which apparently has no commit in its version string)
wkg 0.4.1
what else? It sure seems that somehow the resolution pathing in cargo component's resolution is off, or I'm getting some version crossed.
Brian (Aug 08 2024 at 21:26):https://github.com/squillace/ralph-messed-up/blob/main/Cargo.toml#L23
Should be...
[package.metadata.component.target.dependencies]
thanks @Brian ! That was it.cargo component v0.15.0 creates [package.metadata.component.dependencies] -- missing the infix target
Ralph (Aug 12 2024 at 09:48):rather, the cargo component new --lib command with that version creates the older toml section name.
Ralph (Aug 12 2024 at 09:49):Taylor Thomas said:
Ralph Yeah this is still a work in progress. We are close to getting done with adding pulling from a registry: https://github.com/bytecodealliance/cargo-component/pull/322
There will still be some follow ups after that but we're getting there
@Taylor Thomas does this PR also fix the "cargo component new --lib` toml section name? Not critical if it doesn't; I'll file an issue if not.
Ralph (Aug 12 2024 at 12:27):
Taylor Thomas (Aug 14 2024 at 01:51):No it doesn't fix that issue
Last updated: Nov 25 2024 at 19:03 UTC