About the RSM Technical Discussion! category

guillemcordoba · March 24, 2021, 10:37am

Yes, tryorama is usable again. You can see the dna build tutorial repo for a full working example of everything.

I don’t have the bandwidth to go through that cycle, more so as windows doesn’t have native nix support. And I think that apart from that there is one piece in holochain core that doesn’t have windows support yet. I’ve been going through that experience of advancing through things without any or little documentation, and it feels great to share the discoveries afterwards. I encourage you to go through it if you really want something to work (eg in Windows without any VM), as of now everything is yet to be built (templates, tutorials, guides), and I’ve found myself overworked with everything, so it would be great to have others be involved in that as well

dellams · March 24, 2021, 11:09am

Yeah know the feeling about being overworked brother! lol also battling through health and adrenal issues, which has unfortunately slowed me down a lot but we will get there in the end!

HODL!

dellams · March 24, 2021, 2:51pm

Knew it was too good to be true! lol

I just tried running the conductor again today and got back another new fun error! lol

[nix-shell:~/holochain-rsm2/elemental-chat-develop/elementalChatHapp]$ hc sandbox generate ElementalChat.happ
hc-sandbox: Creating 1 conductor sandboxes with same settings
hc-sandbox: Config ConductorConfig { environment_path: EnvironmentRootPath("/tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP"), use_dangerous_test_keystore: false, signing_service_uri: None, encryption_service_uri: None, decryption_service_uri: None, dpki: None, keystore_path: Some("/tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP/keystore"), passphrase_service: None, admin_interfaces: Some([AdminInterfaceConfig { driver: Websocket { port: 0 } }]), network: None }
hc-sandbox: Created directory at: /tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP Keep this path to rerun the same sandbox
hc-sandbox: Created config at /tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP/conductor-config.yaml

Conductor ready.
Error: Failed to install app: Expected AdminResponse::AppBundleInstalled but got Error(InternalError(“Conductor returned an error while using a ConductorApi: EntryDefStoreError(DnaError(WasmError(Compile(“link error: Import not found, namespace: env, name: __debug”))))”))

[nix-shell:~/holochain-rsm2/elemental-chat-develop/elementalChatHapp]$

Which is very odd considering it was working yesterday fine?

Any ideas guys? Thanks.

You have to laugh rather than cry! lol

dellams · March 27, 2021, 6:48pm

Any ideas anyone? I’m keen to get this working ASAP, it will then enable the .NET HDK to finally be finished and bring the flood of devs, PR and resources we all need! Thanks

dellams · March 31, 2021, 12:24pm

I went back to the standalone ubuntu install because I am blocked as I said above.

But on that I get a different error:

david@david-System-Product-Name:~$ nix-shell https://holochain.love
these derivations will be built:
/nix/store/9333vz9a8zkvwlmrknpkbz13s187nipc-rust-1.48.0-2020-11-16-7eac88abb.drv
/nix/store/wvy5hdbikg16png07345v0r4vbi82sa6-source.drv
/nix/store/gp3sy26xj1cjm9ff5ks9x1vrgv9ncrm8-lair-keystore-vendor.tar.gz.drv
/nix/store/0mkrii7mqq7kyimqzx6q904dh51d83jp-lair-keystore.drv
/nix/store/spyyygb6m17f9j417qxy72dhb9a0rmi9-source.drv
/nix/store/bm63nh5pzas4m6c1q6v54w98wjp81dfy-holochain-vendor.tar.gz.drv
/nix/store/jhp3w38j6z39w6mjrbh0brmnzi5dqri8-holochain.drv
/nix/store/ndl58c0vza711vi4lp3h2yi088l6p8z5-holochain.drv
/nix/store/ysx0i9k33dl9dpxb8hk9ycpf1yalwf27-holochain.drv
error: creating log file ‘/nix/var/log/nix/drvs/93//33vz9a8zkvwlmrknpkbz13s187nipc-rust-1.48.0-2020-11-16-7eac88abb.drv.bz2’: Permission denied
david@david-System-Product-Name:~$

Any ideas? Thanks.

dellams · March 31, 2021, 3:54pm

I tried the crate way and that worked fine until I ran the holochain command, which gave this error:

Well, this is embarrassing.

holochain had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at “/tmp/report-f6c586ab-f108-44bf-b551-a5dc1fa5d9ff.toml”. Submit an issue or email with the subject of “holochain Crash Report” and include the report as an attachment.

Homepage: GitHub - holochain/holochain: The new, performant, and simplified version of Holochain on Rust (sometimes called Holochain RSM for Refactored State Model)

Authors: Holochain Core Dev Team devcore@holochain.org

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!

But I cannot find the tmp folder? Like the new error message, that was something new at least!

Cheers
D.

Connoropolous · March 31, 2021, 7:30pm

Can you post anything that was written above this? or was there nothing?

dellams · April 3, 2021, 8:06pm

Was nothing above it.

dellams · April 16, 2021, 12:51pm

Any ideas guys? Been waiting 23 days for a response now… Would be appreciated thanks.

[nix-shell:~/holochain-rsm2/elemental-chat-develop/elementalChatHapp]$ hc sandbox generate ElementalChat.happ
hc-sandbox: Creating 1 conductor sandboxes with same settings
hc-sandbox: Config ConductorConfig { environment_path: EnvironmentRootPath("/tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP"), use_dangerous_test_keystore: false, signing_service_uri: None, encryption_service_uri: None, decryption_service_uri: None, dpki: None, keystore_path: Some("/tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP/keystore"), passphrase_service: None, admin_interfaces: Some([AdminInterfaceConfig { driver: Websocket { port: 0 } }]), network: None }
hc-sandbox: Created directory at: /tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP Keep this path to rerun the same sandbox
hc-sandbox: Created config at /tmp/tmp.xqmx7dSJtZ/VS7ZNAipLD2AIFCFc3fnP/conductor-config.yaml

Conductor ready.
Error: Failed to install app: Expected AdminResponse::AppBundleInstalled but got Error(InternalError(“Conductor returned an error while using a ConductorApi: EntryDefStoreError(DnaError(WasmError(Compile(“link error: Import not found, namespace: env, name: __debug”))))”))

[nix-shell:~/holochain-rsm2/elemental-chat-develop/elementalChatHapp]$

guillemcordoba · April 18, 2021, 9:38am

Oh wow yeah that’s unfortunate. holochain.love doesn’t work with hc unfortunately, and I would suggest not using that at all and instead move on to locking the holochain version with a default.nix file. This way you don’t depend on a constantly updating url that may break your code, and you can be much more deliberate about your setup and align it with your collaborators.

Here is an working example defaullt.nix file. Inside it, you’ll find the holochain hash that it will compile against, if you want to change it in the future. Let me know if you have any questions around that. Here you can find the setup instructions for the gym which explain a bit the reasonale around this way of using nix.

dellams · April 19, 2021, 4:48pm

Ok great thanks bro, so do I just put that file in the root of my holochain folder and override the old file?

Then I just enter the shell again?

Then it will re-setup everything and should just work then?

It’s odd everything did seem to be working until I tried running the sandbox a 2nd time?

Cheers.
D.

guillemcordoba · April 19, 2021, 5:07pm

Mmm if by “root of my holochain folder” you mean the holochain core github repository, then no. You don’t need to have that cloned anymore.

If you copy that default.nix file in the root of the repository for your project, and then run nix-shell, you’ll have everything setup again and any collaborators in that project will have also the same holochain version.

So, if you follow exactly the same structure and instructions that are there in holochain-dna-build-tutorial, everything should just work.

The-A-Man · April 21, 2021, 6:22am

If we clone your DNA-build-tutorial project, nix-shell into it, then cc ../ into our project, the tools (holochain, hc, etc) would still continue to work in that directory where we cc"ed", no? [That has worked fine for be thus far…]

But I guess you “recommend” that we keep that nix file in our project folder, right? It’s just a recommendation, no?

Or is it absolutely necessary (for reasons unknown to me) that the nix file be present in the happ’s project directory?

Or put simply, is cc ../my-project after nix-shell . into holochain-DNA-build-tutorial a safe action?

That way, my-project won’t have to bear the weight of the filthy dirty stuff that .nix files are; haha!

However, to explicitly specify the version of dependencies (of the tooling that the nix file provides, not to mention version-locking with a specific branch/revision of the holochain/holochain repo) the project depends upon, I think it would make sense to put the nix file in the project directory…

But as far as the zome code is concerned, it can be pretty oblivion of the hc/holochain tooling that one is using, since

[dependencies]
hdk = “0.0.100”

specifies it all (now that the hdk crate(s) have been published on crates-io). One might not be able to build the zomes (especially into a DNA file) without adequate tooling though.

dellams · April 29, 2021, 2:52pm

I tried this but when I run the sandbox for the ElementalChat as per your guide I am still getting the same error:

[nix-shell:~/holochain-rsm3/elemental-chat-develop/elementalChatHapp]$ hc sandbox generate ElementalChat.happ
hc-sandbox: Creating 1 conductor sandboxes with same settings
hc-sandbox: Config ConductorConfig { environment_path: EnvironmentRootPath("/tmp/tmp.lD2nYBApYu/POGeQTYAuzYCq5RaN5WE1"), use_dangerous_test_keystore: false, signing_service_uri: None, encryption_service_uri: None, decryption_service_uri: None, dpki: None, keystore_path: Some("/tmp/tmp.lD2nYBApYu/POGeQTYAuzYCq5RaN5WE1/keystore"), passphrase_service: None, admin_interfaces: Some([AdminInterfaceConfig { driver: Websocket { port: 0 } }]), network: None }
hc-sandbox: Created directory at: /tmp/tmp.lD2nYBApYu/POGeQTYAuzYCq5RaN5WE1 Keep this path to rerun the same sandbox
hc-sandbox: Created config at /tmp/tmp.lD2nYBApYu/POGeQTYAuzYCq5RaN5WE1/conductor-config.yaml

Conductor ready.
Error: Failed to install app: Expected AdminResponse::AppBundleInstalled but got Error(InternalError(“Conductor returned an error while using a ConductorApi: EntryDefStoreError(DnaError(WasmError(Compile(“link error: Import not found, namespace: env, name: __debug”))))”))

[nix-shell:~/holochain-rsm3/elemental-chat-develop/elementalChatHapp]$

Any ideas? Thanks.

guillemcordoba · April 29, 2021, 4:04pm

That seems like a mismatch in versions: the one that compiles and created ElementalChat.happ, and the one with which you are running the hc sandbox command. Are you bundling the happ yourself?

dellams · May 17, 2021, 4:06pm

Great thanks. Ok I started again from scratch and now it is working for your sample zomes, yay!

Haven’t tried elementalchat again yet, may have been an issue with that? But for now it just needs to be any zome so I can test HoloNET RSM to see if I can get the MessagePack stuff working, as you may recall?

Problem I now have is I am getting this error from HoloNET when it attempts to connect over a websocket:

Error Occured. Resason: Error occurred connecting to ws://localhost:8888
Error Details: System.Net.WebSockets.WebSocketException (0x80004005): Unable to connect to the remote server
—> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it.

I can’t work out where the issue is, .NET connecting through WSL2, or WSL2 through nix-shell or issue with the conductor itself?

I have a feeling it is an issue with WSL2 blocking the connection? But I have no idea how to solve this? I thought it might be the Windows Firewall but I disabled that and still same issue.

I even tried WireShark to try and find the issue but I dont know what I am looking for in the big capture file I get from that! lol Like looking for a needle in a haystack! lol

The capture file is below:
https://drive.google.com/file/d/10YJ-8mR0rVY5CFtbBCUr1TvLNnjWaLeI/view?usp=sharing

Would be near the bottom of the file, because I stopped capturing as soon as the error message was thrown.

I was looking for ws://localhost:8888 in the destination column but there is none with that so that is a bit odd? Not sure if anyone has any experience with WireShark here? Or anyone here knows more about networking? Especially on Windows and WSL2?

Would be really appreciated thanks.

At least some progress finally, now just got to get this working so we can then finally get back to testing the MessagePack part!

Cheers
D.
P.S. Is there any Web UI client I can test with the conductor to see if that can connect through WSL2? Is there anyone else here who have got it all working on WSL2? Be great to here your feedback thanks!

@pauldaoust @hedayat @guillemcordoba @Connoropolous @sidsthalekar @e-nastasia

dellams · May 17, 2021, 5:18pm

Good news everyone, worked out why, its because for some unknown MAD reason port forwarding is off by default with WSL2! Crazy I know!

You need to create a .wslconfig file in the root of your userspace so for me that is C:\Users\David.

In the file you just need:

[wsl2]
localhostForwarding=true

So now after a long 8 months waiting I can FINALLY get on with HoloNET RSM! lol

The error I now get from the conductor is below:

May 17 18:04:55.193 ERROR holochain_websocket::websocket: Websocket: Bad message type Pong([])
May 17 18:04:55.240 ERROR holochain_websocket::websocket: websocket_error_from_network=Utf8

Not sure what Pong means though? lol

Here is what I am sending:

Any ideas?

Thanks Tribe.
D.

dellams · May 17, 2021, 5:26pm

As a reminder, here is what we were discussing back in Feb when I last managed to get HoloNET to connect on my Linux standalone install…

dellams · May 17, 2021, 5:38pm

Ok, I changed the HoloHash and AgentPubKey to binary arrays and that got rid of the pong error but the Conductor still gives this error:

May 17 18:33:50.757 ERROR holochain_websocket::websocket: websocket_error_from_network=Utf8

It doesn’t give anymore than that, are there any logs or something I can look at for more info?

Here is what I am now sending:

Getting closer…

Cheers.
D.

dellams · June 7, 2021, 2:11pm

Anyone?