Why can this only be used on these subnets?
I can’t answer why, since it pertains to the underlying PocketIC server. Maybe @mraszyk can shine some light on that.
In the meantime, the best I could personally come up with for Motoko is to inject the canister ID at runtime using init args. For example here, and tested here.
Can you try with the current beta version and see if it improves the situation?
npm i -D @hadronous/pic@beta
It’s way better (thanks!) but, long lasting tests still fail.
Vitest 1.6.0 + "hadronous/pic 0.8.1
RUN v1.6.0 /Users/daviddalbusco/projects/juno/juno
✓ src/tests/satellite.storage.spec.ts (34 tests) 2707ms
✓ src/tests/console.storage.spec.ts (51 tests) 2502ms
✓ src/tests/satellite.upgrade.spec.ts (14 tests) 61130ms
✓ src/tests/orbiter.upgrade.spec.ts (6 tests) 23157ms
✓ src/tests/satellite.auth.spec.ts (16 tests) 1630ms
✓ src/tests/satellite.spec.ts (21 tests) 1588ms
✓ src/tests/satellite.datastore.spec.ts (18 tests) 3966ms
✓ src/tests/orbiter.spec.ts (11 tests) 1338ms
✓ src/tests/mission-control.set-unset.spec.ts (10 tests) 3203ms
✓ src/tests/console.upgrade.spec.ts (1 test) 10239ms
✓ src/tests/console.metadata.spec.ts (3 tests) 4370ms
✓ src/tests/satellite.custom-domains.spec.ts (11 tests) 2372ms
✓ src/tests/console.custom-domains.spec.ts (9 tests) 3612ms
↓ src/tests/satellite.playground.spec.ts (1 test | 1 skipped)
✓ src/tests/console.spec.ts (1 test) 10116ms
Test Files 14 passed | 1 skipped (15)
Tests 206 passed | 1 skipped (207)
Start at 14:31:31
Duration 135.97s (transform 185ms, setup 0ms, collect 394ms, tests 131.93s, environment 0ms, prepare 41ms)
Vitest 2.0.4 + hadronous/pic@beta
RUN v2.0.4 /Users/daviddalbusco/projects/juno/juno
✓ src/tests/satellite.auth.spec.ts (16 tests) 5303ms
✓ src/tests/satellite.spec.ts (21 tests) 5416ms
✓ src/tests/satellite.storage.spec.ts (34 tests) 8230ms
✓ src/tests/console.storage.spec.ts (51 tests) 8418ms
✓ src/tests/orbiter.spec.ts (11 tests) 5656ms
✓ src/tests/satellite.datastore.spec.ts (18 tests) 14554ms
✓ src/tests/mission-control.set-unset.spec.ts (10 tests) 9910ms
✓ src/tests/satellite.custom-domains.spec.ts (11 tests) 4120ms
↓ src/tests/satellite.playground.spec.ts (1 test | 1 skipped)
✓ src/tests/console.custom-domains.spec.ts (9 tests) 4459ms
✓ src/tests/console.metadata.spec.ts (3 tests) 10443ms
✓ src/tests/console.spec.ts (1 test) 9457ms
✓ src/tests/console.upgrade.spec.ts (1 test) 18656ms
❯ src/tests/orbiter.upgrade.spec.ts (6 tests | 2 failed) 38849ms
× Orbiter upgrade > v0.0.6 -> v0.0.7 > Page views > should still list all entries after upgrade
→ Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
× Orbiter upgrade > v0.0.6 -> v0.0.7 > Page views > should be able to collect new entry and list both bounded and unbounded serialized data
→ Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/tests/satellite.upgrade.spec.ts (14 tests | 1 failed) 81419ms
× Satellite upgrade > v0.0.15 -> v0.0.16 > should keep listing existing heap collections as such
→ Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
FAIL src/tests/orbiter.upgrade.spec.ts > Orbiter upgrade > v0.0.6 -> v0.0.7 > Page views > should still list all entries after upgrade
FAIL src/tests/orbiter.upgrade.spec.ts > Orbiter upgrade > v0.0.6 -> v0.0.7 > Page views > should be able to collect new entry and list both bounded and unbounded serialized data
FAIL src/tests/satellite.upgrade.spec.ts > Satellite upgrade > v0.0.15 -> v0.0.16 > should keep listing existing heap collections as such
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/3]⎯
Test Files 2 failed | 12 passed | 1 skipped (15)
Tests 3 failed | 203 passed | 1 skipped (207)
Start at 14:27:51
Duration 85.43s (transform 354ms, setup 1ms, collect 4.22s, tests 224.89s, environment 2ms, prepare 1.45s)
Did you try increasing the test timeout? I’m using a pretty long 60,000ms in my own tests. They involve some pretty heaving lifting with a full NNS so you probably don’t need that long.
This limitation is dropped in the upcoming PocketIC release that I’m about to announce on the forum tonight. If you’re interested in more details why there was such a limitation, then I’m happy to share more about the PocketIC server internals.
I would say so because currently the test ends after a minute
✓ src/tests/satellite.upgrade.spec.ts (14 tests) 61130ms
But, I can try to add some extra timeout for those that are failing that’s a good point. I’ll have a try and report.
Spotted this error, it should be resolved with adding more timeout?
❯ npm run test src/tests/mission-control.set-unset.spec.ts
> @junobuild/juno@0.0.31 test
> vitest src/tests/mission-control.set-unset.spec.ts
RUN v2.0.4 /Users/daviddalbusco/projects/juno/juno
Test Files no tests
Tests no tests
Start at 18:12:06
Duration 5.22s (transform 12ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 0ms)
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: The PocketIC binary took too long to start. Please try again.
❯ intervalMs node_modules/@hadronous/pic/dist/pocket-ic-server.js:82:19
❯ Timeout.runPoll [as _onTimeout] node_modules/@hadronous/pic/dist/util/poll.js:10:32
close timed out after 10000ms
Tests closed successfully but something prevents Vite server from exiting
You can try to identify the cause by enabling "hanging-process" reporter. See https://vitest.dev/config/#reporters
That’s odd… Is that happening consistently?
That timeout is not configurable because I never seen it taking more than 5 seconds to start the server.
Ah no good point. Trying again, it passes now.
Is the https outcalls feature added in the current release? And what about Bitcoin Integration?
@mraszyk @NathanosDev
Is the
https outcallsfeature added in the current release?
Yes.
And what about
Bitcoin Integration?
This is on the roadmap, but I can’t give an estimate just yet when it becomes available.
Did anyone ever get to the bottom of
console.error
PocketIC server encountered an error UpdateError { message: "Instance was deleted" }
It seems to happen a good bit and then reruning seem to fix it…but it would be nice to get rid of it.
What version are you on?
This particular project is still on 0.8.1 as it works with my nns state.
Those issues are generally improved in the current beta version.
I’ll give it a try when I get a chance to generate a new network state.
I could successfully test this draft PR for bitcoin integration in PocketIC following the developer docs. So I’m hopeful we could get it released in a week or two.
@NathanosDev Will the current beta have access to use the server while a test is running. I’m trying to do:
const agent = await new HttpAgent({
host: process.env.PIC_URL
});
await agent.fetchRootKey();
and I get
AgentError: Server returned an error:
Code: 404 (Not Found)
Body:
at HttpAgent._HttpAgent_requestAndRetry (node_modules/@dfinity/agent/src/agent/http/index.ts:628:11)
at async HttpAgent._HttpAgent_requestAndRetry (node_modules/@dfinity/agent/src/agent/http/index.ts:626:14)
at async HttpAgent._HttpAgent_requestAndRetry (node_modules/@dfinity/agent/src/agent/http/index.ts:626:14)
at async HttpAgent._HttpAgent_requestAndRetry (node_modules/@dfinity/agent/src/agent/http/index.ts:626:14)
at async HttpAgent.status (node_modules/@dfinity/agent/src/agent/http/index.ts:968:22)
at async HttpAgent.fetchRootKey (node_modules/@dfinity/agent/src/agent/http/index.ts:980:24)
my pic url is PIC_URL http://127.0.0.1:54903 but maybe the server is setting something else upt to host the replica stuff?
The version of PocketIC used in the Pic-JS beta doesn’t yet expose the agent-compatible server so that won’t work. It’s a high priority for me to get this done, I just haven’t had much time recently.
But out of curiosity, what are you trying to do that you need it?
I got it working and commented over at How to validate a certificate from JS/TS - #19 by skilesare
I think I thought that the agent was pulling the root from mainnet because I didn’t specify a host and I was using agent.fetchRootKey to get it(it may have been from main net). (I’m not quite sure because I found out all the keys start with the same prefix),I figure out that I needed to specify the host but that didn’t seem to work because, as you say, no HTTP agent. Eventually I figured out that I use NNS state I need to get the pub key of the nns subnet and if I only have a singe app subnet I can use that pub key. Code is working here: icrc75.mo/pic/icrc75/list.test.ts at 4899454fdf3f544376a4c116c1627279c6e2b901 · icdevsorg/icrc75.mo · GitHub