Stream: wasmtime

Topic: Warg Server + wkg wit build

view this post on Zulip Lorenzo (Feb 02 2025 at 05:08):

Hello,

I have set up a warg server and have successfully published a package, example:hello@0.1.0.

I configured my warg & wkg to use the private registry. But when I run wkg wit build, I get the following error:

Error: Unable to resolve dependencies

Caused by:
    0: registry error: EOF while parsing a value at line 1 column 0
    1: EOF while parsing a value at line 1 column 0

I can see these logs on warg-server:

Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.424813Z  INFO warg_server::api: starting GET /.well-known/wasm-pkg/registry.json
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.424850Z  INFO tower_http::trace::on_response: finished processing request latency=42 μs status=404
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.478089Z  INFO warg_server::api: starting GET /v2/
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.478124Z  INFO tower_http::trace::on_response: finished processing request latency=41 μs status=404
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.493968Z  INFO warg_server::api: starting GET /v2/
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.494004Z  INFO tower_http::trace::on_response: finished processing request latency=41 μs status=404
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.509961Z  INFO warg_server::api: starting GET /v2/example/hello/tags/list
Feb 02 05:05:39 staging.registry warg-server[2469]: 2025-02-02T05:05:39.509996Z  INFO tower_http::trace::on_response: finished processing request latency=40 μs status=404

When I try to request GET /v2/example/hello/tags/list I get a 404 not found.

Is wit expecting a newer version of warg-server? I am trying to find a version in GitHub that has the v2 endpoints but haven't had much luck so far.

On another note, would I have better luck using OCI registry instead of Warg in terms of stability etc?

view this post on Zulip Lorenzo (Feb 02 2025 at 06:38):

I think I found out the problem. It seems to default to OCI, need to specify that it's a warg registry instead in the config file:

[registry."some.registry.origin.example.com"]
default = "warg"

view this post on Zulip Lorenzo (Feb 02 2025 at 09:40):

So that previous issue has been resolved, but now I am running into something else. I am publishing this package to the registry:

hello.wit

package example:hello;

world hello {
  export greet: func(name: string);
}

hello.js

export const greet = (name) => {
  console.log(`hello ${name}!`);
};

But it looks like when I build the component, it overrides the namespace, package and world names. Instead of example:hello/hello it becomes root:component/root, so it doesn't find the package because the resolver is looking for the original name.

Last updated: Feb 27 2025 at 22:03 UTC