Fix #3810, re-enable checkStellarCoreMajorVersionProtocolIdentity #4321
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes #3810 by re-enabling a slightly-altered version of the checkStellarCoreMajorVersionProtocolIdentity function. The change makes the function aware of the vNext build configuration, which I think was the only thing making it not-work for the futurenet build that was broken in #3808
@sisuresh could you take a look and confirm that this ought to do the trick? it seems too simple (and we've been deferring fixing this for ages) but I couldn't think of a reason why this wouldn't be sufficient.