-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__get_agent_activity
unknown env variable conductor error
#10
Comments
Very weird. My only guess is possible platform updates but I wouldn't think that could be right what with Nix flakes... latest version, have cloned from scratch or run |
tried doing both of those suggestions but still getting the same error. |
This looks like a Holochain version mismatch between the build environment and the running environment. They did rewrite Holonix to use nix flakes, and maybe there's an error somewhere where a version is underspecified somehow. What platform are you both using? I'm going to see if I can recreate this on my M1 processor. |
mac M1 |
I actually get quite a lot of warnings which indicate that peer dependencies might be underspecified. I also get the same issue on my M1: https://hackmd.io/@adaburrows/B1T9zSS-3 |
Related?- h-REA/hREA#392 (comment) |
It looks like this is actually related to downloading the DNAs instead of building them locally. The version of Holochain installed isn't pinned to the minor version number. For instance, I have Holochain v0.1.3 installed when I run nix develop instead of 0.1.1 which is what the flake file looks like it wants, but at least on my Apple M1 it doesn't honor that. |
To fix this it looks like you'll need to update the line in the flake.nix to not use underscores:
|
ARRRRG! It turns out if I do that, then it just doesn't build on my M1. I'm going to try Holochain 0.1.2 next.
|
Ok, the build for version 0.1.2 works on Apple M1. If you're not using it already, you should upgrade so we can actually collaborate on this code. Maybe we should probably also try to pin this for the whole ecosystem for now, so every zome in every project should be theoretically compatible. |
Oh, as much as it pains me to say it. The version 0.1.3 is much more fleshed out in terms of Nix. Perhaps we need to change it to that. |
So @adaburrows you think that the issue is that the |
There's two problems:
So we need to pin the proper version that works on Apple silicon (0.1.3 is sufficient) and we need to be able to download the zomes for the version of Holochain that is pinned in Nix. Currently, I see there is a version of hREA zomes built for 0.1.3. So that part is done. I'm going to get PRs in for our repos to update the flake.nix to Holochain v0.1.3. My test on our NH Launcher repo worked, so I can get that in soon. |
pinned to 0.1.3 now, But @weswalla is still getting the error... |
Oops, hadn't pushed! Try it now after re-entering your Nix env, 39a67fe should fix. |
Ah, yeah, without a pinned version it would have automatically installed v0.2.0 instead of v0.1.3. |
when trying to run this app:
nix develop
pnpm i
pnpm start
I get the following conductor error:
[1] Error: Failed to install app: Expected AdminResponse::AppInstalled but got Error(InternalError("Conductor returned an error while using a ConductorApi: RibosomeError(WasmRuntimeError(RuntimeError { source: User(WasmError { file: \"crates/holochain/src/core/ribosome/real_ribosome.rs\", line: 426, error: Compile(\"Error while importing \\\"env\\\".\\\"__get_agent_activity\\\": unknown import. Expected Function(FunctionType { params: [I32, I32], results: [I64] })\") }), wasm_trace: [], native_trace: 0: <unknown>\n 1: <unknown>\n 2: <unknown>\n 3: <unknown>\n 4: <unknown>\n 5: <unknown>\n 6: <unknown>\n 7: <unknown>\n 8: <unknown>\n 9: <unknown>\n 10: <unknown>\n 11: <unknown>\n 12: <unknown>\n 13: <unknown>\n 14: <unknown>\n 15: <unknown>\n 16: <unknown>\n 17: <unknown>\n 18: <unknown>\n 19: <unknown>\n 20: <unknown>\n 21: <unknown>\n 22: <unknown>\n 23: <unknown>\n 24: <unknown>\n 25: <unknown>\n 26: <unknown>\n 27: <unknown>\n 28: <unknown>\n 29: <unknown>\n 30: <unknown>\n 31: <unknown>\n }))"))
The text was updated successfully, but these errors were encountered: