Missed null check in docker_image_dest.go #2164
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
As the documentation says, "It is always OK to pass nil instead of a SystemContext." Signed-off-by: Bojidar Marinov <[email protected]>
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.
As the documentation says, "It is always OK to pass nil instead of a SystemContext."
I failed to get a suitable minimal reproduction project, but I got a panic on this line while using the library to copy images around once it decided to recompress a few layers, and I have confirmed that applying the change locally (or passing a suitable DestinationCtx to copy.Image) fixes the panic. Still, let me know if an actual reproduction would be necessary to get this merged.