Dave Kelsey

@yqcong why would you not want to use caliper 0.4.2 ?

caliper 0.4.2 can work with any existing fabric 1.4 network, I have no idea about caliper 0.2 sorry. I would suggest you use caliper 0.4.2 to benchmark your network.

But you said you had modified the 1.4 source code, not the 1.2 code base

@DDlovei Please could you provide more detail, for example the chaincode method that is a problem, your workload module that you are trying and what you have tried so far...

This doesn't appear to be relevant to caliper-benchmarks but a potential issue with caliper

The problem is one of indentation, the options property is associated with the module, but in the above example the options is associated with the transaction property which is not...

Looks like you are trying to use an old version of caliper which doesn't recognise the config files in the benchmark repo. I would recommend using caliper 0.4.2

I've now been able to run the simple scenario using caliper 0.4.2 with no issues with the workload files, this could have been a problem with 0.4.0. Please try again...

For fabcar: 1. delete go.mod and go.sum files 2. update the dependencies in the code change ``` "github.com/hyperledger/fabric/core/chaincode/shim" sc "github.com/hyperledger/fabric/protos/peer" ``` to ``` "github.com/hyperledger/fabric-chaincode-go/shim" sc "github.com/hyperledger/fabric-protos-go/peer" ``` ensure you have...

for fixed-asset and fixed-asset-base 1. delete go.mod and go.sum files 2. delete the vendor directory 3. run `go mod init fabric/api/fixed-asset/go` 4. run `go mod tidy` 5. run `go mod...