Closed m0bi5 closed 2 years ago
Unfortunately what you are trying to do isn't supported. There are (horrible) tricks to make it work and that is currently how the caliper integration tests make it work but it isn't right. There is a plan to alter this in the main branch of caliper and make it so the integration tests test in a more natural way while still working direct from source code.
Why are you using the caliper source rather than the pre-packaged node modules or even the caliper docker image which uses the pre-packaged node modules ?
@davidkel So that I can implement what you have said in #1245. Or will that work without having to build caliper from source?
@m0bi5 I have a PR awaiting review to fix that issue and once it's merged there will be an unstable caliper build which would include it (both a npm module and a docker image) Another way you could do this would be to install the npm module when building your docker image then patch the file rather than cloning the source. It should be easy to do that approach.
@m0bi5 the fix has been merged and should be in available using docker pull hyperledger/caliper:0.5.0-unstable-20220304102214
as well as an npm module for the cli npm install @hyperledger/caliper-cli@0.5.0-unstable-20220304102214
@davidkel Thanks a lot, the release works!
Which Caliper version are you using?
v0.4.2
Which Node.JS version are you using?
10.22
Which operating system are you using?
Alpine
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
I am building caliper from source in a docker container -
And I run it using the following docker-compose file
What was the observed incorrect behavior?
Caliper uses the v1 FabricGateway even when I pass the
--caliper-bind-sut fabric:2.2
flag. It works as expected when I use thehyperledger/caliper:0.4.2
image so I think it has something to do with the local installation.Please provide the error logs and their surroundings.