You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just got round to playing again after @guillemcordoba asked me to test his bump to the latest version of holonix and I had an error which I created an issue for #38. That seems to work ok now however when I run the tests I get a different issue which seems to be to do with an outdated version of Tryorama from what I can gather.
Wasn't sure whether it was to do with the holonix version or something else so creating new issue. Also not sure what to do with the old issue so will see what the response from this one is and go from there.
thanks!
[nix-shell:~/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests]$ npm test
> [email protected] test
> npm run check-nix && npm run build && npm run pack && TRYORAMA_LOG_LEVEL=info RUST_LOG=error WASM_LOG=warn RUST_BACKTRACE=1 TRYORAMA_HOLOCHAIN_PATH="holochain" ts-node src/index.ts
> [email protected] check-nix
> ./../../../../check_running_in_gym_nix_shell.sh
> [email protected] build
> cd .. && CARGO_TARGET_DIR=target cargo build --release --target wasm32-unknown-unknown
Compiling exercise v0.0.1 (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/zomes/exercise)
Finished release [optimized] target(s) in 1.86s
> [email protected] pack
> hc dna pack ../workdir
Wrote bundle /Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/workdir/exercise.dna
18:47:04 [tryorama] info: Using the following settings from environment variables:
18:47:04 [tryorama] info: {
"adminInterfaceId": "tryorama-interface-admin",
"appInterfaceId": "tryorama-interface-app",
"stateDumpOnError": true,
"zomeCallTimeoutMs": 90000,
"conductorTimeoutMs": 125000,
"strictConductorTimeout": false,
"chooseFreePort": false,
"logLevel": "info",
"portRange": [
33000,
34000
],
"legacy": false,
"singletonAppId": "TRYORAMA_APP",
"holochainPath": "holochain",
"lairPath": "lair-keystore"
}
TAP version 13
# say a greeting
FIXME: ignoring onJoin
18:47:04 [tryorama] info: Spawning lair for test with keystore at: /tmp/tmp.uv4tQkoZq0/tryorama/Gi2DSa/keystore
18:47:04 [tryorama] info: Using conductor path: holochain
18:47:04 [tryorama] info: Holochain version: holochain 0.0.100
18:47:04 [tryorama] info: Conductor config path: /tmp/tmp.uv4tQkoZq0/tryorama/Gi2DSa/conductor-config.yml
18:47:05 info:
☉☉☉ [[[CONDUCTOR c0]]]
☉
☉ ###HOLOCHAIN_SETUP###
☉ ###ADMIN_PORT:33000###
☉ ###HOLOCHAIN_SETUP_END###
☉
18:47:05 info:
★★★ [[[CONDUCTOR c0]]]
★ Conductor ready.
★
18:47:05 [tryorama] info: Conductor 'c0' process spawning completed.
App Port spun up on port 54886
18:47:06 info:
☯☯☯ {{{CONDUCTOR c0}}}
☯ FATAL PANIC PanicInfo {
☯ payload: Any { .. },
☯ message: Some(
☯ called `Option::unwrap()` on a `None` value,
☯ ),
☯ location: Location {
☯
18:47:06 info:
☸☸☸ {{{CONDUCTOR c0}}}
☸ file: "crates/kitsune_p2p/kitsune_p2p/src/gossip/simple_bloom.rs",
☸ line: 169,
☸ col: 14,
☸ },
☸ }
☸ thread 'holochain-tokio-thread' panicked at 'called `Option::unwrap()` on a `None` value', crates/kitsune_p2p/kitsune_p2p/src/gossip/simple_bloom.rs:169:14
☸ stack backtrace:
☸
18:47:06 info:
☮☮☮ {{{CONDUCTOR c0}}}
☮ note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
☮
18:47:21 [tryorama] error: Test error: 'Error: Timed out in 15000ms: activate_app\n' +
' at Timeout.<anonymous> (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/@holochain/conductor-api/src/websocket/common.ts:16:14)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
not ok 1 Test threw an exception. See output for details.
---
operator: fail
at: <anonymous> (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/@holochain/tryorama/src/middleware.ts:137:13)
stack: |-
Error: Test threw an exception. See output for details.
at Test.assert [as _assert] (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/tape/lib/test.js:304:54)
at Test.bound [as _assert] (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/tape/lib/test.js:91:32)
at Test.fail (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/tape/lib/test.js:398:10)
at Test.bound [as fail] (/Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/tape/lib/test.js:91:32)
at /Users/steve/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests/node_modules/@holochain/tryorama/src/middleware.ts:137:13
...
^C
[nix-shell:~/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests]$ npm audit report
# npm audit report
axios <0.21.1
Severity: high
Server-Side Request Forgery - https://npmjs.com/advisories/1594
No fix available
node_modules/axios
@holochain/tryorama *
Depends on vulnerable versions of axios
node_modules/@holochain/tryorama
2 high severity vulnerabilities
Some issues need review, and may require choosing
a different dependency.
[nix-shell:~/Holoplay/holochain-gym/developer-exercises/1.basic/1.entries/exercise/tests]$
The text was updated successfully, but these errors were encountered:
Just got round to playing again after @guillemcordoba asked me to test his bump to the latest version of holonix and I had an error which I created an issue for #38. That seems to work ok now however when I run the tests I get a different issue which seems to be to do with an outdated version of Tryorama from what I can gather.
Wasn't sure whether it was to do with the holonix version or something else so creating new issue. Also not sure what to do with the old issue so will see what the response from this one is and go from there.
thanks!
The text was updated successfully, but these errors were encountered: