Fix canonicalization of layer IDs #36
Merged
Conversation
This file contains hidden or 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
rhatdan
reviewed
Apr 19, 2017
| fromLayer, ok := r.lookup(from) | ||
| if !ok { | ||
| fromLayer, ok = r.lookup(toLayer.Parent) | ||
| to = toLayer.ID |
Member
There was a problem hiding this comment.
It looks like this same block of code is copied three times, shouldn't we just add a new function to handle it?
Member
Author
There was a problem hiding this comment.
Yeah, that's a better idea. Fixing that.
Fix canonicalization of layer IDs when computing layer differences, which we also broke in #6. Signed-off-by: Nalin Dahyabhai <[email protected]>
Member
Author
|
Okay, this gets buildah's self-tests working again. |
Member
|
LGTM Much better |
Member
Author
|
Okay, merging it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix canonicalization of layer IDs when computing layer differences, which we also broke in #6.