Local replica update - Unexpected WasmEngineError: Couldn't find compiler binary

Developers
1

Hi, I’m looking to upgrade to the latest version of the replica in my custom CLI (see PR https://github.com/junobuild/juno-docker/pull/38). However, when I do so, I encounter the following runtime error:

juno-satellite-1  | ⚠️  CLI Error: Error: Call was rejected:
juno-satellite-1  |   Request ID: f33a1d99ab2862a225a09c3972c333499481771092fde26bd7b281c1fac0eb79
juno-satellite-1  |   Reject code: 5
juno-satellite-1  |   Reject text: Error from Canister qhbym-qaaaa-aaaaa-aaafq-cai: Canister encountered a Wasm engine error: Unexpected WasmEngineError: Couldn't find compiler binary

Do you know what this error means and how to resolve it?

Can the foundation provide the steps required to migrate from replica version ec35ebd252d4ffb151d2cfceba3a86c4fb87c6d6 to 3d6a76efba59d6f03026d6b7c1c9a1dfce96ee93?

If there are any release notes, documentation or CHANGELOGS available, of course please feel free to just point me in that direction.

2

You need to pull a new compiler_sandbox binary similar to how to you pull the existing canister_sandbox.

1 Like
3

Oh, that’s the secret ingredient :wink:. It seems to work like a charm. Thanks, Ulan!

1 Like
4

Just a note for the future: If it’s possible to include these types of changes to the replica in a CHANGELOG, I’d definitely like it. However, I for sure understand this might be a rather niche request.

5

Good point! I guess our mode of operation so far was that replica is used on mainnet, dfx, and pocket-ic only.

1 Like
6

That might be good. So, now you know there’s another consumer. :wink:

P.S.: Again, I’m aware it’s a niche request. Thanks for your answers!

1 Like
7

Released in Juno Docker images v0.0.32 (in case anyone is ever wondering).