-
Hi, I have written my contract based on 'fabric-contract-api' package and I can successfully install, instantiate, invoke and query my smart contract using basic fabric network.
Now I want to analyze…
-
i get the follwing error
cse@system:~$ **sudo npx caliper benchmark run --caliper-workspace ./ --caliper-benchconfig ~/caliper/packages/caliper-samples/benchmark/drm/config.yaml --caliper-networkco…
-
Traceback:
```
[backend-org-2-substra-backend-worker-56c79d57bd-tdv9b worker] [2019-12-09 21:33:15,334: ERROR/ForkPoolWorker-1] exception calling callback for
[backend-org-2-substra-backend-worker…
-
Hi, @MCLDG !
The amazon managed blockchain service and your repo resources are awesome!
I really appreciate what you have done!
During the chaincode development phase I have installed a lot c…
-
If you have 2 channels with a smart contract deployed to both with the same name then submit transaction doesn't always go to the right channel
-
## Context
We have a custom fabric network setup with custom chaincodes that we want to test with Caliper. However i have created a network config file, added our custom chaincodes and written …
ghost updated
5 years ago
-
@horeaporutiu
Trying to run commercialPaperLoopback-master with the fabric-samples/commercialPaper example.
Edited network.yaml and local_fabric/connection.json to replace ports 17050/17051/170…
-
When I tested the example chaincode:chaincode_example02, the parameters received by the chaincode were incorrect
I use the command `peer chaincode invoke -o orderer:7050 -C mychannel -n chaincod…
-
Caliper does not reuse connections when sending transactions to Fabric orderers, potentially causing timeouts.
## Context
I am running performance testing against Fabric, while monitoring the pe…
-
PR #108 introduces a chaincode name prefix for private chaincodes. As this is a technical limitation and may disappear in the future we decided to hide this prefix from the end user.
PR #108 comes …