It's less about a race and more about consistency. (A race can cause an inconsistency.) Imagine that when you run the contract on peer one, the sequence observed by the ledger is ["data1", "data2"]; o

#fabric-chaincode #fabric-questions

Hi, Concurrency (using goroutine and go channel) can cause non-deterministic behavior in fabric. I have not found any source or example on the use of Goroutines and go channels in fabric contracts; I

#fabric-chaincode #fabric-questions

Hi there, I'm was trying to find out if this is possible on the SO and reading the CouchDB documentation, but could not find anything that would work on the Fauxton web client to test it. I have a dat

#couchdb #fabric-chaincode

Hi Malik, The contract API is used to invoke a chaincode usually deployed as separate instance (could be on the same or different channel). When you need to call a method inside your chaincode you jus

#fabric-chaincode

Hello Guys, Just a quick question. I have this scenario where I'm calling one method inside a chaincode A (let's say to update some properties based on external factors). Now, these external factors a

#fabric-chaincode

Hi, No, you don't have to start each contract individually in the main() function. In the Contract.NewChaincode() pass the multiple Contracts. Thanks, Nidhi Singh

#fabric-chaincode

How to deploy multi contracts in one chaincode package? In single contract examples, there is a main() function starts the defined contracts by shim.Start(). In multi contracts scenario, do I need to

#fabric-chaincode

Hi Nik, You are right! Defining the policy using the MSP ID's of the organizations, everything works as expected. Thank You. Stefano

#policies #fabric-chaincode #fabric-questions #fabric-endorser

You may need to use the MSP ID's of the organizations, rather than the informal names. Try this policy: "OR('Org1MSP.peer','Org2MSP.peer')"

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Hi Community, Still facing the same issue. Additional log from monitordocker.sh net_test: "peer0.org2.example.com|2021-03-29 12:22:25.948 UTC [discovery] chaincodeQuery -> ERRO 066 Failed constructing

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Hi Nik, Thanks for answering. I confirm the chaincode has been committed to the channel: peer lifecycle chaincode commit -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --peerAddres

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Hi, Can you confirm that the chaincode has been committed to the channel? Or can you do a docker ps to confirm that the chaincode containers have started. This error looks like the chaincode may not b

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Using the default configuration I can run all the functions inside the application folder of commercial paper on test-network without any problem If I edit the default signature policy in the approval

#policies #fabric-chaincode #fabric-questions #fabric-endorser

I decided to apply a workaround and set as comments the part of the test creating this problem (Will this be a problem?). I just want to see what is coming next. So, the next problem is that adoptopen

#fabric-chaincode #fabric-questions

Brett did you find anything about rapsberries? Is there a list for fabric-chaincode-java with people willing to help?

#fabric-chaincode #fabric-questions

I can not solve the issue in ./gradlew clean build install: org.hyperledger.fabric.contract.ContractRouterTest > testStartingContractRouterWithStartingAChaincodeServer FAILED java.lang.AssertionError:

#fabric-chaincode #fabric-questions

I changed the grpc version to build.gradle file from 1.23.0 to 1.37.0-SNAPSHOT (latest) which was installed to local mvn repo and I solved the issue.No I have an new one :( | Results: FAILURE (229 tes

#fabric-chaincode #fabric-questions

I have already tried that. The same error.

#fabric-chaincode #fabric-questions

I believe you need to add `mavenLocal()` to https://github.com/hyperledger/fabric-chaincode-java/blob/master/fabric-chaincode-protos/build.gradle#L13 like it is mentioned here: https://github.com/hype

#fabric-chaincode #fabric-questions

Hello, I have built 1) protobuf 3.12.0 using ../autogen, /configure, make, make check, sudo make install. No problems, the protobuf pack is installed in usr/local/lib 2) export LDFLAGS="-L/usr/local/l

#fabric-chaincode #fabric-questions