Dave Kelsey

@aklenik The generator builds are now going through ok and the build referenced in this PR has gone. There is code to detect a failure but I'm guessing a check...

So you are saying that it achieves the specified tps value if no timeout error occurs ? but if you get a timeout then the reported tps is wrong ?...

As of caliper 0.4.2 which is the current version that should be used, new versions of the fabric connectors for caliper were introduced along with a new network configuration format....

This will be either a configuration problem either in the fabric network or the connection profile. The other thing that could cause this is a chaincode crash, either way this...

A roundrobin mechanism is the simplest, but it may be good to also support weighting as well so we can control load distribution

this may be of interest https://github.com/grpc/grpc/blob/master/doc/load-balancing.md https://grpc.io/blog/grpc-load-balancing/

@aklenik with the precision option then it decides based on number of significant digits so can result in `1e+2` type of output for example whereas fixed fixes the number of...

This is duplicated here https://stackoverflow.com/questions/71936538/running-hyperledger-caliper-to-test-my-local-hyperledger-fabric-network/71937097#71937097 @Mohammed-alzuharey I've answered this in stackoverflow

This might be a good test of the node module caching in the build, so maybe leave until that is implemented

I found where the verification field is used and is meant for end user consumption rather than caliper engine consumption. In the docs ``` `IsVerified():boolean` indicates whether we are sure...