Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

secscan: continue iterating after failure (PROJQUAY-2563) #894

Merged

Conversation

crozzy
Copy link
Contributor

@crozzy crozzy commented Sep 17, 2021

If Clair returns an error the current behaviour is to
error out, thus not indexing any subsequent manifests.
This change allows the worker to continue indexing
subsequent manifests after one failure.

Signed-off-by: crozzy joseph.crosland@gmail.com

crozzy and others added 3 commits September 17, 2021 13:10
If Clair returns an error the current behaviour is to
error out, thus not indexing any subsequent manifests.
This change allows the worker to continue indexing
subsequent manifests after one failure.

Signed-off-by: crozzy <joseph.crosland@gmail.com>
…#896)

Follow-up to 694fa2a. Correctly set the expected value for the
pagination token when not blocking on a failed API request.
Updating funcparserlib to 1.0.0a0 fixes the issue initially addressed
in d3809b2.
Copy link
Contributor

@flavianmissi flavianmissi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Github isn't flagging any conflicts, so this is just an FYI: the updates to requirements-osbs.txt and requirements.txt have already landed on redhat-3.6

@flavianmissi flavianmissi merged commit 1b06153 into quay:redhat-3.6 Oct 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants