Skip to content
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

Update to Fabric v2.1.1 #369

Merged
merged 1 commit into from
Jun 12, 2020

Conversation

g2flyer
Copy link
Contributor

@g2flyer g2flyer commented Jun 10, 2020

What this PR does / why we need it:
Subject says it (mostly) all. Upgrade to latest Fabric release, now also upgrading go modules (which were still on v2.0.1 before ...).

See release notes for more info on v2.1.1 (most noticeable for us was that external builder stopped handling some symlinks it has handled in past ...)

Note: for go modules, just updating the fabric dependency in go.mod didn't work (everything built, tests run but go vet failed). To make it work i did a go get -u .$pkg with pkg for all github.com/hyperledger/fabric*' packages found in go.mod .. and then did a go mod tidy at end. Hope that was the correct process; at least it seemed to work ;-)

Which issue(s) this PR fixes:

Related to issue #370

Special notes for your reviewer:

To test, you will have to move the tag on fabric from v2.1.0 to v2.1.1.

Does this PR introduce a user-facing changes and/or breaks backward compatability?:

Signed-off-by: Michael Steiner <michael.steiner@intel.com>
@g2flyer g2flyer requested review from a team, bvavala and MHBauer June 10, 2020 00:53
@g2flyer g2flyer linked an issue Jun 10, 2020 that may be closed by this pull request
Copy link
Contributor

@mbrandenburger mbrandenburger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to work fine in my docker setting.

Interestingly, I cannot reproduce the go vet issue you are mentioning. What I did: I just checkout out your PR; started a fresh docker container with cd utils/docker; make run,
inside the container I checkout the fabric v2.2.1 tag and finally hit make inside docker. All smooth.

@g2flyer
Copy link
Contributor Author

g2flyer commented Jun 10, 2020

Interestingly, I cannot reproduce the go vet issue you are mentioning. What I did: I just checkout out your PR; started a fresh docker container with cd utils/docker; make run,
inside the container I checkout the fabric v2.2.1 tag and finally hit make inside docker. All smooth.

Sorry if i was not clear: the go vet issue shouldn't occur in the current version of the pr. it did only occur when i only changed the fabric (core) repo from 2.0.1 to 2.1.1, but not the other fabric modules/repos. (at some level, having to uplevel also other fabric packages is not 100% surprising; what was surprising that i got the problem only with go vet but not with building and testing our code ..

@mbrandenburger mbrandenburger merged commit bd94291 into hyperledger:master Jun 12, 2020
@g2flyer g2flyer deleted the msteiner.fabric-2.1.1 branch June 26, 2020 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Keep Uptodate with latest Fabric Releases
3 participants