-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add scan failure duration setting #705
Conversation
Signed-off-by: Paolo Di Tommaso <[email protected]>
Signed-off-by: Paolo Di Tommaso <[email protected]>
@munishchouhan quick double check on this ? |
ok sure |
Signed-off-by: munishchouhan <[email protected]>
@pditommaso in case of build and mirror docker client retries, but how will this help in case of scan? |
Yeah, just realised the same. |
Let me try one thing |
i tried like this
|
Signed-off-by: Paolo Di Tommaso <[email protected]>
Think it's needed to delete the |
so where does the retry will happen in this case, i sent the request twice, still same:
|
It's not a retry, the scanId in the store should be deleted, so once there's a new request a new one is assigned e.g. xxx_1 -> xxx_2 |
one thing i notice, even if i select --scan-mode required. log is printing: |
Signed-off-by: Paolo Di Tommaso <[email protected]>
Signed-off-by: Paolo Di Tommaso <[email protected]>
Signed-off-by: Paolo Di Tommaso <[email protected]>
The problem was solved by this 239fffd |
This PR adds Scan failure duration setting