I think this issue is related to PR#303

#fabric #hyperledger-fabric

I was able to duplicate, and it seems isolated to the go-application for asset transfer (basic). I can deploy the go chaincode on the network and call it with the javascript application and it works f

#fabric #hyperledger-fabric

I am running assetTransfer.go sample program out of asset-transfer-basic directory. My test network is up. I know that its up and running correctly because I can interact with it -- I can exercise var

#fabric #hyperledger-fabric

Just to avoid duplication of effort: https://stackoverflow.com/questions/63628826/error-cannot-find-module-fabric-client-in-fabric-1-2

#fabric-sdk-node #hyperledger-fabric

Hello Abhay, Are you using Amazon managed blockchain by chance? If so, they may be multiple versions behind where you would be if you were using native Fabric deployment on AWS. If you are using a nat

#fabric-sdk-node #hyperledger-fabric

Error : Cannot find Module 'fabric-client' in fabric 1.2 Even after trying "npm update" command, still i am facing fabric-client error. The error details given below Fabric version - 1.2 | OS - Amazon

#fabric-sdk-node #hyperledger-fabric

Hi Chris, Here is the package command: # peer lifecycle chaincode package chaincode.tar.gz --path chaincode/chaincode/javascript/ --lang nod e --label counter_v1 2020-08-28 06:04:04.548 UTC [bccsp] Ge

#fabric-chaincode #hyperledger-fabric #fabric-sdk-node

Hi Bozhidar, Can you share the commands/output from when you packaged the chaincode? You may also find it helpful if you have not already done so, to review the tutorial “Deploying a Smart Contract to

#fabric-chaincode #hyperledger-fabric #fabric-sdk-node

Hello All, The peer has joined the channel and chaincode is packed on. I have a problem with instantiating chaincode in Hyperledger fabric Network version 2: # peer lifecycle chaincode install chainco

#fabric-chaincode #hyperledger-fabric #fabric-sdk-node

If you try to install miniFabric to centos, you will see that cant work under published condition, i.e. Docker version (18.03 or newer)...

#minifabric #hyperledger-fabric #network #centos #minifab

Got it Dave. Sorry, I am a bit new to 'git' terminologies. We have planned to switch to latest HLF v1.4.x release to be in sync for now. Thank you for the quick clarifications.

#fabric-questions #fabric #hyperledger-fabric

There is no 'tree' for v1.4.4. v1.4.4 is a point-in-time tag that cannot be updated. The branch with latest 1.4.x fixes is "release-1.4". If you need to stay on v1.4.x for now, you should build from "

#fabric-questions #fabric #hyperledger-fabric

Hi Brett, thanks it works fine with new URL now. I wanted to know if we plan to backport the fix to v1.4.4 tree too? Plus, I found one more issue in the building the source code of HLF v1.4.4. I have

#fabric-questions #fabric #hyperledger-fabric

Hi Chintan, We migrated to Artifactory late last year, you can see the updated URL in later 1.4 releases: https://github.com/hyperledger/fabric/blob/release-1.4/Makefile#L84 chintanr97@... --- [

#fabric-questions #fabric #hyperledger-fabric

I recently learnt that the nexus.hyperledger.org URL is no longer valid. However, in v1.4.4 tree of the HLF, we still make use of it at least in Makefile to download (curl) the 'chaintool' files. I wo

#fabric-questions #fabric #hyperledger-fabric

I tested miniFabric with Java ABstore chaincode from HLF fabric-sample code. Maybe some need to know how :) I don`t find examples of using at minifab github pages. And this work! Tested. date;./minifa

#minifab #hyperledger-fabric #fabric-sdk-java #windows10 #minifabric

Hi, I filed a bug for this: https://github.com/litong01/minifabric/issues/43 If you have WSL2, the same repo and commands work there. I suggest using the WSL CLI. Disabling the WSL2 Docker integration

#fabric #minifab #windows10 #hyperledger-fabric #network

I installed minifab to windows 10... I worked with WSL 2 and HLF on windows... Here is error which was received on command: C:\Users\Owner\mywork> C:\Users\Owner\mywork>minifab.cmd generate Minifab Ex

#fabric #minifab #windows10 #hyperledger-fabric #network

The second version of the chaincode would have to support both the old and new data. There are various approaches possible: You could attempt to unmarshal the JSON using new data structure, and if it

#fabric #database #couchdb #fabric-chaincode #hyperledger-fabric

I've a query on how we need to deal with data structure changes in chaincode. Lets say, you have deployed the chaincode in production and lot of data stored in ledger and world state db(Couchdb). If y

#fabric #database #couchdb #fabric-chaincode #hyperledger-fabric