Closed jost-s closed 2 years ago
@jost-s, I don't know what version of tryorama you are using, I mention this because it seems like you are using a much older version of holochain. I see you are using a DNA with .dna.gz
file format. This would be created if you are still using dna-utils
binary. Currently, after the hc
binary release, the new file format ends with .dna
or .happ
.
@zo-el I have cloned the tryorama repo and run the example test as is.
My holochain version is 0.0.100
[nix-shell:~/Desktop/dev/holochain/tryorama/example]$ holochain --version
holochain 0.0.100
The tryorama version is 0.4.3
{
"name": "@holochain/tryorama",
"repository": {
"type": "git",
"url": "https://github.com/holochain/tryorama"
},
"version": "0.4.3",
"description": "test framework for holochain hApps",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"directories": {
"test": "test"
},
Maybe the test dna in the example
folder is not up to date?
@jost-s Interesting, that looks to be an oversite. This is the new test DNA that is been used for testing tryorama. I will clean this up. Sorry for the inconvenience.
Not at all, @zo-el. Thanks for the hint 👌
Running
npm test
in the example folder from a nix shell with nightly holochain build throws an error:I've debugged into the (fairly complex) code and and got to the point that it happens when the
client
sends the message to register thetest.dna
to the AdminWebSocket. The response is the above error then.I don't understand the architecture enough yet to know where the registering fails on the admin web socket. Perhaps @Connoropolous or @zo-el can see on the spot where the problem is?