We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
为了开始新项目; 先编辑了对应 配置 $ rg -Tcss "qfab"
go.mod 1:module qfab main.go 6: "qfab/sdkInit" 14: srv_root = "/home/zoomq/go/src/qfab" config.yaml 12: path: /home/zoomq/go/src/qfab/fixtures/crypto-config 38: path: /home/zoomq/go/src/qfab/fixtures/crypto-config/peerOrganizations/org1.example.com/users/User1@org1.example.com/tls/client.key 40: path: /home/zoomq/go/src/qfab/fixtures/crypto-config/peerOrganizations/org1.example.com/users/User1@org1.example.com/tls/client.crt 156: path: /home/zoomq/go/src/qfab/fixtures/crypto-config/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem 185: path: /home/zoomq/go/src/qfab/fixtures/crypto-config/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem 204: path: /home/zoomq/go/src/qfab/fixtures/crypto-config/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem
(base) zoomq @ ubuntu-s-1vcpu-2gb-sgp1-01 ~/go/src/qfab
docker 先启动后:
$ cd fixtures && docker-compose up -d
Creating network "fixtures_test" with the default driver Creating volume "fixtures_orderer.example.com" with default driver Creating volume "fixtures_peer0.org1.example.com" with default driver Creating volume "fixtures_peer1.org1.example.com" with default driver Creating couchdb1 ... done Creating couchdb0 ... done Creating orderer.example.com ... done Creating ca.org1.example.com ... done Creating peer1.org1.example.com ... done Creating peer0.org1.example.com ... done
(base) zoomq @ ubuntu-s-1vcpu-2gb-sgp1-01 ~/go/src/qfab/fixtures
$ cd .. (base) zoomq @ ubuntu-s-1vcpu-2gb-sgp1-01 ~/go/src/qfab
$ go build
# github.com/hyperledger/fabric-sdk-go/internal/github.com/hyperledger/fabric/discovery/client ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/api.go:47:28: undefined: discovery.ChaincodeCall ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:83:53: undefined: discovery.ChaincodeInterest ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:120:55: undefined: discovery.ChaincodeCall ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:124:13: undefined: discovery.ChaincodeInterest ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:229:95: undefined: discovery.ChaincodeCall ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:247:54: undefined: discovery.ChaincodeCall ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:604:38: undefined: discovery.ChaincodeInterest ../../pkg/mod/github.com/hyperledger/fabric-sdk-go@v1.0.0/internal/github.com/hyperledger/fabric/discovery/client/client.go:620:25: undefined: discovery.ChaincodeCall
同, 另外征信项目相同尝试时, 也一样: 不时出现 discovery.ChaincodeCall 无法完成编译 · Issue #4 · sxguan/education
The text was updated successfully, but these errors were encountered:
有解决吗
Sorry, something went wrong.
我也有相同地问题。
Hi, how to solve this?
No branches or pull requests
为了开始新项目;
先编辑了对应 配置
$ rg -Tcss "qfab"
(base) zoomq @ ubuntu-s-1vcpu-2gb-sgp1-01 ~/go/src/qfab
docker 先启动后:
$ cd fixtures && docker-compose up -d
(base) zoomq @ ubuntu-s-1vcpu-2gb-sgp1-01 ~/go/src/qfab/fixtures
$ cd ..
(base) zoomq @ ubuntu-s-1vcpu-2gb-sgp1-01 ~/go/src/qfab
$ go build
同, 另外征信项目相同尝试时, 也一样:
不时出现 discovery.ChaincodeCall 无法完成编译 · Issue #4 · sxguan/education
The text was updated successfully, but these errors were encountered: