-
Notifications
You must be signed in to change notification settings - Fork 403
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
Caliper using v1 connector even when SUT set to 2 #1250
Comments
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 ? |
@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) |
@m0bi5 the fix has been merged and should be in available using |
@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.
The text was updated successfully, but these errors were encountered: