Closed a-moreira closed 1 year ago
Running into the same issue as described by @a-moreira.
For added context...
Running yarn devphase contract test
also fails with the following log (Node version 16.20.0
)
Here you can find list of available releases: https://github.com/Phala-Network/phala-blockchain/releases
First you need to ensure devphase and Phala binaries are compatible - it is ensured only for latest binaries and latest devphase. In diffrent case - for example older Phala binaries release (which IMO should not be used) you need to find older devphase which was working with it.
Tested with example 'nightly-2023-05-26' - works fine
@FaisalAl-Tameemi for your case I would need to know more details. IMO this is different case and you should create separate issue for it. For the first glance you've used to old Phala release
@l00k ok thanks. created a separate issue.
P.S. I'm also using latest
so thought it was relevant.
@l00k I can run the stack with nightly-2023-05-26
that you mentioned, but I still get the "RPC is not ready" errors when trying to deploy a contract on the Phat Contracts UI (both locally run and at https://phat.phala.network/)
@a-moreira
On local network default node port is 9944 and worker port is 8000. (Unless you changed it)
Hey folks, I was able to resolve this by changing devphase
to @devphase/cli
and @devphase/service
along with updating the config file.
Here's a draft PR which does not include fixing the associated tests yet.
P.S. I think the timeouts set in the config might be too short for some machines. Extending that might help as well.
I'm trying to run the Phala stack inside
phat
viayarn devphase stack run
and connect to Phat Contracts UI (https://phat.phala.network/) to it, but without success.If I change the stack version in![image](https://github.com/Phala-Network/phat-offchain-rollup/assets/48456867/732b3d07-8285-4347-8dd7-99e7bfbc81e1)
devphase.config.ts
tolatest
, I'm then able to run the stack, but still get some errors on the UI. For example, when connecting to the stack locally, I get:But it works if I point to PoC-5 testnet:![image](https://github.com/Phala-Network/phat-offchain-rollup/assets/48456867/b6e9bf7d-e638-4ce8-8894-6e3615bca65f)
I get the same behavior using a local instance of Phat Contracts UI (from https://github.com/Phala-Network/phat-contract-ui).
specs: