Open chinmay241 opened 4 years ago
So 1. means it is a bad implementation in Caliper side. Adding delay does not help, this just changes the race condition. Instead, you need a real health check from Caliper to the node/network. But you are right, they just do the sleep there, this is not good. Let's ignore this for now and work with executing against a running network.
With regards to 2, this would mean there is probably the wrong web3j version used somewhere. This means, it is either wrong in Caliper or just in your local environment? Try to install the correct version in your local npm in a version that has the method.
In that case the 1.2.2 version would have the method eth.getChainId
Will hopefully fixed by https://github.com/hyperledger/caliper/pull/862.
Tested in both these environment: 1) If the Geth+Caliper both come up together Errors:
2) Geth is running and you just run Caliper. Errors:
So I can see solution for the:
1) is adding some delay before executing the smart contract step. The node takes a while so does WS it tries connecting and it fails with no Open Connection.
2) Its about the method web3.eth.getChainId which is not a function; I can see something here about this here: https://github.com/ethereum/web3.js/pull/3113 Core issue: https://github.com/ethereum/web3.js/issues/3070 need to understand this better ^^