I'm trying to move everything to 2.2 version using same chaincode but getting an error while installing channel 'transactcc':
Error: error getting chaincode deployment spec for transactcc: 'go list' failed with: package transactcc is not in GOROOT (/usr/local/go/src/transactcc): exit status 1
Please advise.
Also will appreciate a lot for a migrate 1.4 to 2.2 doc\any experience shared.
Thanks in advance!
The fix was for a changes in GO mod, following command fixed the issue:
go env -w GO111MODULE=off
Related
I am trying to instantiate a Golang chaincode on my Hyperledger Fabric network (setup on cloud) using Fabric Node SDK. However, I am facing the following error while performing the same:
Error: error starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:latest: API error (404): manifest for hyperledger/fabric-ccenv:latest not found: manifest unknown: manifest unknown
The stack trace for the same is:
at self._endorserClient.processProposal (./node_modules/fabric-client/lib/Peer.js:140:36)
at Object.onReceiveStatus (./node_modules/grpc/src/client_interceptors.js:1207:9)
at InterceptingListener._callNext (./node_modules/grpc/src/client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (./node_modules/grpc/src/client_interceptors.js:618:8)
at callback (./node_modules/grpc/src/client_interceptors.js:845:24)
I also tried to directly pull the image hyperledger/fabric-ccenv in my local environment but getting a similar error there as well:
Command:
docker pull hyperledger/fabric-ccenv
Error:
Using default tag: latest
Error response from daemon: manifest for hyperledger/fabric-ccenv:latest not found: manifest unknown: manifest unknown
Fabric Peer Version: 1.4.4
Fabric Node SDK Version: 1.4.4
As mentioned by alpha above, latest tag for hyperledger/fabric-ccenv does not exist anymore.
The value is defined as chaincode.builder in core.yaml file and can be overridden by the environment variable CORE_CHAINCODE_BUILDER.
So, the correct approach to solve the issue is passing the environment variable to peer with preferred ccenv version. For example:
CORE_CHAINCODE_BUILDER: hyperledger/fabric-ccenv:2.1
See this commit as an example of how to use it in a Helm chart.
latest tag isn't available anymore. you have to use specific tag. Below is the snippet of dave comment infabric-maintainers group.
The Hyperledger Fabric maintainers are pleased to announce the availability of Fabric v2.2.0!
v2.2 continues to build on the v2.0 foundation with additional improvements and fixes. For details, check out the release notes:
https://github.com/hyperledger/fabric/releases/tag/v2.2.0
Additionally we are happy to announce that v2.2 is the next long-term support (LTS) release for Hyperledger Fabric. v2.2.x will be the target release for most fix backports, while the most important fixes will continue to be backported to v1.4.x as well.
More details of the LTS strategy can be found in the RFC that was merged earlier this year:
https://github.com/hyperledger/fabric-rfcs/blob/master/text/0000-lts-release-strategy.md
Finally, it is worth noting that the 'latest' tag on dockerhub images has been retired. We felt that the tag was too confusing, given that there is a combination of regular releases and LTS releases available now - the definition of 'latest' may not be the same for everyone.
Give v2.2 a try and let us know what you think!
https://hyperledger-fabric.readthedocs.io/en/release-2.2/install.html```
link: https://chat.hyperledger.org/channel/fabric-maintainers?msg=dCMSGymRoWPiJ8fiv
I was trying to install/instantiate a year old chaincode and obviously I haven't updated any dependencies so I also ran into this issue.
This particular [hyperledger/fabric-ccenv:latest] docker pull is being done by one of dependencies and following is the way around that.
Do a docker pull of fabric-ccenv for whatever version you want.
docker pull hyperledger/fabric-ccenv:2.1
And then tag it as latest,
docker tag hyperledger/fabric-ccenv:2.1 hyperledger/fabric-ccenv:latest
Now when you try to install the chaincode, the docker pull for latest image wont happen as the image with the tag is already available on your machine.
The above two commands is something you can add in your start script.
Thanks to #alpha for mentioning that the latest tag has been taken down.
I have been running my code which involves deployment of smart contract to Ethereum Ropsten network. I ran this successfully for some time but last week did installed another software after which I started getting these errors:
command: solc --combined-json abi,asm,ast,bin,bin-runtime,clone-bin,devdoc,interface,opcodes,userdoc
return code: 1
stderr:
stdout:
Invalid option to --combined-json: clone-bin
I have no clue why I'm getting them. Anyone can help?
Ok I have solution now. Solidity has a newer version of solidity which is v0.5.1 which is not compatible with py-solc so what should be done to following the instructions here install version 0.4.25 and set SOLC_BINARY env pointing to your binaries.
I am new in blockchain development. Actually i done a demo in composer vertion .16.6. Now i upgrade my composer vertion from 0.16.6 to 0.19.14. And i changed the code in createPeerAdmin.sh file for suitable to vertion 0.19.14. But always showing an error that
Connection profile has no x-type property defined. It is not valid for this version of composer
Please help me as possible.
Thanks
try to reset the environment variable for before starting or setup the development server using the following command by changing the fabric version u're going to use specific version from the development servers.
cd ~/fabric-dev-servers
export FABRIC_VERSION=hlfv11
./startFabric.sh
./createPeerAdminCard.sh
You can also find better information about the installation of the documentation in the link below:
https://hyperledger.github.io/composer/v0.19/installing/development-tools.html
Attempting to follow the hyperledger fabric 1.2.0 developers chaincode tutorial.
I was unable to get the hyperledger fabric dependencies by executing
go get -u github.com/hyperledger/fabric/core/chaincode/shim. I tried deleting the hyperledger/fabric source folder from my GOPATH's src directory as suggested here, but the same error messages keep popping up:
github.com/hyperledger/fabric/vendor/github.com/docker/docker/pkg/archive
../github.com/hyperledger/fabric/vendor/github.com/docker/docker/pkg/archive/archive.go:364:5: hdr.Format undefined (type *tar.Header has no field or method Format)
../github.com/hyperledger/fabric/vendor/github.com/docker/docker/pkg/archive/archive.go:364:15: undefined: tar.FormatPAX
../github.com/hyperledger/fabric/vendor/github.com/docker/docker/pkg/archive/archive.go:1166:7: hdr.Format undefined (type *tar.Header has no field or method Format)
../github.com/hyperledger/fabric/vendor/github.com/docker/docker/pkg/archive/archive.go:1166:17: undefined: tar.FormatPAX
Skipping the go get command and going straight to go build would output the same error as above.
I've also tried installing gnu-tar to no avail.
Reinstalling the latest stable version of Golang did the trick. At the time of this writing the stable version of go is 1.10.3.
The issue was caused by golang version 1.9.3 having an undefined struct for tar.FormatPAX which was needed for one of the hyperledger fabric go source files.
Non-resolvable parent POM for com.mycompany-community:boot-community-demo:1.0.0-SNAPSHOT: Could not transfer artifact org.broadleafcommerce:broadleaf-boot-starter-parent:pom:5.2.1-SNAPSHOT from/to public snapshots (http://nexus.broadleafcommerce.org/nexus/content/groups/community-snapshots/): Connect to nexus.broadleafcommerce.org:80 [nexus.broadleafcommerce.org/104.130.140.202] failed: Connection timed out: connect and 'parent.relativePath' points at no local POM # line 5, column 13
I am new to Broadleaf & am a UI Developer. I am trying to setup 'Heat Clinic Demo' in my local but unable to do so. Am getting the above errors and unable to proceed further, can someone please help me out in running the project. Thanks in advance
I am not sure how you got that version for your parent but it should be version 5.2.2.1-GA. That is our latest release version. I recommend changing the root pom.xml to use that version instead (in the element).
The Maven error indicates that it could not connect to the Broadleaf nexus. On my end it looks like it is up, verify that you can ping it and try again with -U, e.g. mvn clean install -U to force metadata to be refreshed from the nexus.