This repository has been archived by the owner on Dec 26, 2023. It is now read-only.
Fix manifest fingerprint hash in basic test #48
Merged
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
acostalima
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The basic test is not passing when generating the fingerprint hash for
manifest.json.This PR addresses an issue where the hash length when limited to the generated hash length, the resulting manifest file name would become
manifest..json. Further, the regex for[hash:limit]substitution now only allows a limit between 1 and 32. This was also a problem because the limit could be greater than 32, which would exceed the maximum generated hash length.