Mark S. Lewis
Mark S. Lewis
The change to fabric-protos-go-apiv2 was delivered in PR #108.
See this StackOverflow answer to the same question, demonstrating block eventing working with the Golang client application: https://stackoverflow.com/a/77835368/3680198
I hit this error recently and the problem - for me at least - seemed to be Docker volumes hanging around from a previous time the Fabric network was created....
I'll leave it to Dave and the other maintainers of this repo to give an authoritative answer.
The [legacy Go SDK](https://github.com/hyperledger/fabric-sdk-go) is no longer supported and the accompanying sample client application has been replaced by one using the [Fabric Gateway client API](https://hyperledger.github.io/fabric-gateway/), which is the recommended and...
Which sample application demonstrates the issue? Does running exactly the same sample application work with earlier Fabric versions?
Timeouts on calls are not yet properly implemented in the Fabric Gateway client API, and are currently a mixed bag across different client languages, with some implementations using an arbitrary...
To avoid derailing this documentation issue with implementation of timeouts, I've raised #198
I'm not convinced that a "heartbeat" call on the initial connect is actually helpful. Network or service outages can occur (and be resolved) at any time. The initial heartbeat may...
Yeah, "connect" was used to align with the API terminology of the legacy SDKs. Maybe it would have been better differently named here, but that's what we have now and...