AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: admin ws has not been connected ❯ Conductor.adminWs ../node_modules/@holochain/tryorama/lib/local/conductor.js:268:9 ❯ AppWebsocket.appWs.callZome ../node_modules/@holochain/tryorama/lib/local/conductor.js:246:28 ❯ ProfilesClient.callZome ../node_modules/@holochain-open-dev/utils/src/zome-client.ts:32:24 ❯ ProfilesClient.getAgentProfile ../ui/src/profiles-client.ts:29:15 ❯ ../ui/src/profiles-store.ts:81:22 ❯ fetch ../node_modules/@holochain-open-dev/signals/src/holochain.ts:618:6 ❯ Timeout._onTimeout ../node_modules/@holochain-open-dev/signals/src/holochain.ts:622:26 ❯ listOnTimeout node:internal/timers:573:17 ❯ processTimers node:internal/timers:514:7 This error originated in "src/profile.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "create Profile". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

The job was canceled because "macos-latest" failed.

The operation was canceled.

The job was canceled because "macos-latest" failed.

The operation was canceled.