add image for testing that analysis doesn't error out when unparseable records are encountered#50
Merged
westonsteimel merged 1 commit intomainfrom Sep 13, 2022
Conversation
westonsteimel
changed the title
westonsteimel
force-pushed
the
analyzer-ensure-no-failure-on-unparseable-records
branch
from
2388974 to
d247c8b
Compare
…parseable records Signed-off-by: Weston Steimel <weston.steimel@anchore.com>
westonsteimel
force-pushed
the
analyzer-ensure-no-failure-on-unparseable-records
branch
from
d247c8b to
1065727
Compare
westonsteimel
requested review from
bot190,
emily-lopez,
svietry and
zburstein
bot190
approved these changes
Sep 13, 2022
westonsteimel
deleted the
analyzer-ensure-no-failure-on-unparseable-records
branch
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
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.
Currently this will serve as a good test image for ENTERPRISE-1943 and the corresponding fix in syft anchore/syft#1200, but could be extended to add in other scenarios where we've encountered these issues in the past