-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
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
How to fix hyperledger issue (undefined: discovery.ChaincodeCall) after updating go lang to 1.20? #260
Comments
Same error from me as well, is there a fix for this?? |
@MrRancy, I got error when I run tests. You too? I do not have solution yet. Sad. |
@MrHIDEn, I am using fabric-sdk-go in a personal package development, and that's when I got this error. don't know, because of this, I am unable to build my package. By the way, what is the version you are using? I am working on v1.20 |
Hey @MrHIDEn, I got it working with these versions, for me, the error was from a different package which is the fabric-protos-go. Probably it's the same for you. Could you give it a try with this version?
|
Hey @Teja-S, Generali my app works on any Go version exept 1.14 but when I run tests I got error provided. // go.mod file
go 1.20
require (
github.com/codahale/sss v0.0.0-20160501174526-0cb9f6d3f7f1
github.com/ghodss/yaml v1.0.0
github.com/hyperledger/fabric-contract-api-go v1.2.1
github.com/hyperledger/fabric-sdk-go v1.0.0
) |
One of error says:
when I go there to // Peers returns a response for a peer membership query, or error if something went wrong
Peers(invocationChain ...*discovery.ChaincodeCall) ([]*Peer, error)
|
That is interested:
Peers(invocationChain ...*peer.ChaincodeCall) ([]*Peer, error)
On my libs installed |
I also encountered this problem.
|
Hi.
I have workig fabric application based on 'Go lang' and 'fabric-sdk-go'.
I just updated it to newer versions of 'Go lang' but without success as library uses internally 'discovery' instead of 'peer'.
I'm using those packages:
Errors:
What should I do to fix that?
Regards
The text was updated successfully, but these errors were encountered: