You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Weaver Fabric Go SDK library was augmented in #2901 (and bugs fixed in #2953). But the Weaver Fabric Go CLI depends on this SDK, for which a new release (post alpha.2) must be made to ensure compatibility. This CLI is therefore not building with its current Go modules configuration. We need to fix it so that it can at least be built locally from source.
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
Either a semantic version of the release you are using such as 1.0.0 or a git
commit hash if you are directly working with code from the git repository.
Hyperledger Cactus Plugins/Connectors Used
Which DLT connectors are you using (Fabric, Quorum, Corda, Besu, etc.)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
VRamakrishna
changed the title
Weaver Go CLI module does not compile afte changes in the associated SDK
Weaver Go CLI module compilation failure
Jan 24, 2024
Describe the bug
The Weaver Fabric Go SDK library was augmented in #2901 (and bugs fixed in #2953). But the Weaver Fabric Go CLI depends on this SDK, for which a new release (post alpha.2) must be made to ensure compatibility. This CLI is therefore not building with its current Go modules configuration. We need to fix it so that it can at least be built locally from source.
See #2971 (comment) for context.
To Reproduce
Navigate to the
weaver/samples/fabric/go-cli
folder and runmake build-local
. This will throw an error.Expected behavior
Navigate to the
weaver/samples/fabric/go-cli
folder and runmake build-local
. This should not throw any errors.Logs/Stack traces
Can help maintainers identify root causes
Screenshots
If applicable, add screenshots to help explain your problem.
Cloud provider or hardware configuration:
Are you running the software on a dev machine or somewhere in the cloud?
Operating system name, version, build:
Use this command:
printf "$(uname -srm)\n$(cat /etc/os-release)\n"
For example
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
Either a semantic version of the release you are using such as
1.0.0
or a gitcommit hash if you are directly working with code from the git repository.
Hyperledger Cactus Plugins/Connectors Used
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: