-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WS support for 0.3.1 #12
Comments
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
|
Will hopefully fixed by hyperledger-caliper/caliper#862. |
Tested in both these environment:
Errors:
Errors:
So I can see solution for the:
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.
Its about the method web3.eth.getChainId which is not a function; I can see something here about this here: Add eth.getChainId method to 1.x web3/web3.js#3113 Core issue: Proposal to stabilize Web3 1.x web3/web3.js#3070 need to understand this better ^^
The text was updated successfully, but these errors were encountered: