Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
However, isn't FABRIC_VERSION and FABRIC_CA_VERSION a two digit number in these scripts (e.g. 2.5), whereas the bootstrap.sh script requires a three digit version for pulling binaries (e.g. 2.5.7).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually in my local copy of network script, I am using 3 digit versions. However I can define a pair of auxiliary variables in order to save both 2 digit and 3 digit version's formats in network script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be enough to make the defaults 3 digit versions? Alternatively, it might be nice if the fabric install script accepted 2 digit versions and "did the right thing" ...and it might be good to use the newer install script instead of bootstrap.sh