Looks like the client failed to send the results to the ordering service node: https://github.com/hyperledger/fabric/blob/release-1.4/peer/common/broadcastclient.go#L63 Not sure why grpc returned EOF

#fabric-chaincode

Btw, FoundationDB org officially supports a document layer (https://github.com/FoundationDB/fdb-document-layer based on MongoDB API) on top of the foundationDB. As it is a multi-modal database, they a

#fabric #fabric-chaincode

Hi The performance study on LevelDB secondary index options is well done. That said, for Fabric, I think it's critical to keep CouchDB as an option. Most of the solutions I look at need the functional

#fabric #fabric-chaincode

Hi Jim, I would like to understand the following: Currently, we support only the query based on a secondary index and JSON from CouchDB (not supporting or planning to support map/reduce functions). Ho

#fabric #fabric-chaincode

Hi everyone, I have this wiered MVCC-conflict issue. It appears occasionally as I benchmark my Java chaincode. I tried everything I possibly could to prevent its occurance. Now, I am going to list the

#hyperledger-fabric #fabric-chaincode #consensus #raft

Not quite... MVCC in validation/commit phase checks the chaincode execution readset key version against current state key version to ensure that the execution results are still valid. Therefore if the

#fabric-orderer #fabric-chaincode

Thank you! That's very helpful. In particular, I see now how dangerous the "blind write" can be. Regards, Marco

#fabric-orderer #fabric-chaincode

I am curious, what use case would require a blind-write vs a read-write? S Rob Murgai Program Director - Hyperledger Fabric IBM Blockchain Raleigh-Durham, NC M: 919.342.8432 | LinkedIn: Rob-Murgai

#fabric-orderer #fabric-chaincode

I think most use cases will want the read-write behavior. Append-only use cases may want the blind write behavior. For example consider an IOT sensor that records a data point hourly. There isn't real

#fabric-orderer #fabric-chaincode

Hi, I am using Hyperledger fabric 1.4.7 and using the fabcar as an example to build a sample network and using the Go sdk. Its the same code base as in the fabric-samples just that I have taken it and

#fabric-chaincode #fabric-sdk-go #hyperledger-fabric

Hello; The Wasm Smart Contracts RFC was discussed on the Contributors Call yesterday. I've added a couple of comments to the Wasm Smart Contract RFC from the discussion. Based on this can ask the main

#fabric-rfcs #fabric-chaincode

Hi, I currently trying to add a new index to my 1.4 network. I have the folders correctly set too. When I update the chaincode with the new index folder I can see that my peers have the package correc

#couchdb #fabric-chaincode

Do you have the peer logs? Regards, Senthil

#couchdb #fabric-chaincode

What should I search for in the peer logs? Some sort of error? Because I can't see the index on the couchdb entries

#couchdb #fabric-chaincode

If couchdb returned an error status code while processing the index, we do log the error but chaincode upgrade would succeed irrespective of that. I would suggest to search for the term index to see w

#couchdb #fabric-chaincode

Hello, guys. I want to send events from commit transaction listener to some message brokers like rabbitmq or apache kafka, my intention is notify others systems to do some action. I found something si

#fabric-chaincode

Snippet of the go code...

#fabric-chaincode #fabric-sdk-go #hyperledger-fabric

Further update: When I check via the cli container, only the hyperledger/fabric/peer/ is available. The hyperledger/fabric-chaincode-go/shim/ and the hyperledger/fabric-protos-go/peer dependencies are

#fabric-chaincode #fabric-sdk-go #hyperledger-fabric

Great thanks Santiago!

#fabric-chaincode #fabric-sdk-go #hyperledger-fabric

Hi Jay, Have you solved the issue? I have the same problem in my case trying to deploy the chaincode using the Caliper tool to perform a performance analysis. In addition to what you mention, I have t

#fabric-chaincode #fabric-sdk-go #hyperledger-fabric