Link Search Menu Expand Document

fabric GitHub

Issue 2976 Include the chaincode hash when installing an already existing chaincode
good first issue When installing a new chaincode on the peer you do get the package id of the chaincode which is good... this allows customers to use that data to go through the approve/commit steps. However the issue is when they are reinstalling an existing chaincode there is nothing in the response to indicate the package id(hash). Install in that case returns a message that the chaincode already exists. We should include the package id of the chaincode in the response when it is already installed on the peer.
Created At 2021-10-07 14:04:14 +0000 UTC
Issue 2916 Add Java example to chaincode as external service documentation
docsgood first issue Per stackoverflow post https://stackoverflow.com/questions/69115892/hyperledger-fabric-java-chaincode-timeout-expired-while-starting-chaincode  , it appears Java chaincode is missing from chaincode as an external service doc topic: https://hyperledger-fabric.readthedocs.io/en/latest/cc_service.html#writing-chaincode-to-run-as-an-external-service
Created At 2021-09-14 15:56:40 +0000 UTC