Problem?

[justjoheinz]

I have a small problem with getting the code to run, following the repository and blog post. I think this probably due to changes in rust and its supported wasm targets. It seems wasm32-wasi is no longer a valid target but wasm32-wasip1 now is.

When I do the golem build app step I currently get:

Collecting sources
  Found sources: /Users/markusklink/Projects/moon/golem-moonbit-example/archive/golem.yaml, /Users/markusklink/Projects/moon/golem-moonbit-example/email/golem.yaml, /Users/markusklink/Projects/moon/golem-moonbit-example/golem.yaml, /Users/markusklink/Projects/moon/golem-moonbit-example/list/golem.yaml
Collecting components
  Found components: archive, email, list
Resolving application wit directories
  Resolving component wit dirs for archive (/Users/markusklink/Projects/moon/golem-moonbit-example/archive/wit, /Users/markusklink/Projects/moon/golem-moonbit-example/archive/wit-generated)
  Resolving component wit dirs for email (/Users/markusklink/Projects/moon/golem-moonbit-example/email/wit, /Users/markusklink/Projects/moon/golem-moonbit-example/email/wit-generated)
  Resolving component wit dirs for list (/Users/markusklink/Projects/moon/golem-moonbit-example/list/wit, /Users/markusklink/Projects/moon/golem-moonbit-example/list/wit-generated)
Selecting profiles, no profile was requested
  Selected default profile release for archive using template moonbit
  Selected default profile release for email using template moonbit
  Selected default profile release for list using template moonbit
Generating RPC artifacts
  Skipping creating generated base wit directory for archive, UP-TO-DATE
  Skipping creating generated base wit directory for email, UP-TO-DATE
  Skipping creating generated base wit directory for list, UP-TO-DATE
  Building wasm rpc stub for archive
    Deleting stub temp build dir target/golem-temp/stub/archive/temp-build
    Creating stub temp build dir target/golem-temp/stub/archive/temp-build
    Generating stub WIT directory to target/golem-temp/stub/archive/temp-build
      Generating stub WIT to target/golem-temp/stub/archive/temp-build/wit/stub.wit
      Adding WIT dependencies from target/golem-temp/generated-base-wit/archive to target/golem-temp/stub/archive/temp-build
        Skipping package dependency wasi:logging
        Copying package dependency demo:archive-interface
          Copying target/golem-temp/generated-base-wit/archive/deps/demo_archive-interface/interface.wit to target/golem-temp/stub/archive/temp-build/wit/deps/demo_archive-interface/interface.wit
        Skipping package dependency demo:archive
        Writing wasm-rpc.wit to target/golem-temp/stub/archive/temp-build/wit/deps/wasm-rpc
        Writing poll.wit to target/golem-temp/stub/archive/temp-build/wit/deps/io
    Generating Cargo.toml to target/golem-temp/stub/archive/temp-build/Cargo.toml
    Generating stub source to target/golem-temp/stub/archive/temp-build/src/lib.rs
  Generating bindings for archive-stub (src/bindings.rs)
Failed to compile the generated stub: failed to find the `wasm32-wasi` target and `rustup` is not available. 
If you're using rustup make sure that it's correctly installed; if not, make sure to install the `wasm32-wasi` target
before using this command

Getting the target list produces

rustup target list | ack "wasm32"                                                                                                   [15:20:06]
wasm32-unknown-emscripten
wasm32-unknown-unknown
wasm32-wasip1 (installed)
wasm32-wasip1-threads
wasm32-wasip2
wasm32v1-none

I am uncertain if I am on the right track and how I can update the source to use the new target. Can you provide some insight?

[vigoo]

Yes the latest rust release broke this a few days ago. We are working on new version of everything (golem, documentation, etc) but it is not published yet.

[justjoheinz]

If this is a rust / golem version problem - which version of rust can I install to make it work?

[vigoo]

It was working with 1.83

[justjoheinz]

Ok, I was able to proceed further, but now I get lots of errors in the compilation steps of moombit regarding open traits etc. They seem to be ffi related mostly and I am uncertain how to fix these.
I also had to fix some occurrences in the repo golem.yaml regarding wit-bindgen-moonbit - the commands are correct though in the blog post.

Here are some errors:

Error: [4036]
    ╭─[/Users/markusklink/Projects/moon/golem-moonbit-example/email/interface/wasi/clocks/monotonicClock/top.mbt:25:14]
    │
 25 │       return @poll.Pollable::Pollable(result)
    │              ────────────┬───────────
    │                          ╰───────────── Cannot create values of the read-only type: Pollable.
────╯

or

Error: [4036]
    ╭─[/Users/markusklink/Projects/moon/golem-moonbit-example/email/interface/wasi/io/streams/top.mbt:77:64]
    │
 77 │                               StreamError::LastOperationFailed(@error.Error_::Error_(@ffi.load32((return_area) + 8)))
    │                                                                ──────────┬──────────
    │                                                                          ╰──────────── Cannot create values of the read-only type: Error_.
────╯

or

Error: [4036]
    ╭─[/Users/markusklink/Projects/moon/golem-moonbit-example/email/interface/golem/rpc/types/top.mbt:96:48]
    │
 96 │                               cleanupList.push({address: address, size: (payload).length() * 4, align: 4})
    │                                                ─────────────────────────────┬────────────────────────────
    │                                                                             ╰────────────────────────────── Cannot create values of the read-only type: @demo/email/ffi.Cleanup.
────╯

My guess is that they are probably follow up errors of some misconfiguration. I hope there will be an updated repo and/or blog post soon. BTW, one hurdle I had to face as well was installing the "golem app build" program. The only way to obtain it seems to be the download/releases page. Why not a cargo install? What does it do, which golem-cli doesn't do? I have not really been able to find an explanation of the software.

[vigoo]

Sorry about that; unfortunately the latest changes are not merged to wit-bindgen yet:
bytecodealliance/wit-bindgen#1100

I was using this branch, just did not want to talk about it in the post much to keep it simple(r), hoping it is going to be merged anyway.

[justjoheinz]

Thanks for your patience. Now all components compiled and are in the local golem cloud.

[justjoheinz]

@vigoo Do you have any idea what is required to run the tests, either from the CLI or within VS Code? With moonc version: v0.1.20250113+2f846af8e I currently get a report saying that there is a compiler error which needs reporting with the moonbit team. This could actually be true, I just wonder if you experienced the same problem?

[vigoo]

I think they last worked when I was just defining the model, playing with the language itself without setting up wasm bindings. So basically before the "Compiling as Golem Components" section in my blog post. It gives me the same error now (with the compiler version I was using two weeks ago: moon 0.1.20241231 (16670d0 2024-12-31))