-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Stop ScanAll not work in case of lots of artifacts. #18044
Comments
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
5 tasks
The execution status is currently not refreshed into database properly. We may need further investigation on that first.
|
chlins
added a commit
to chlins/harbor
that referenced
this issue
May 16, 2023
Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: goharbor#18044 Signed-off-by: chlins <[email protected]>
5 tasks
chlins
added a commit
to chlins/harbor
that referenced
this issue
Jun 1, 2023
Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: goharbor#18044 Signed-off-by: chlins <[email protected]>
chlins
added a commit
to chlins/harbor
that referenced
this issue
Jun 2, 2023
Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: goharbor#18044 Signed-off-by: chlins <[email protected]>
chlins
added a commit
to chlins/harbor
that referenced
this issue
Jun 5, 2023
Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: goharbor#18044 Signed-off-by: chlins <[email protected]>
chlins
added a commit
that referenced
this issue
Jun 5, 2023
Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: #18044 Signed-off-by: chlins <[email protected]>
WilfredAlmeida
pushed a commit
to WilfredAlmeida/harbor
that referenced
this issue
Jul 8, 2023
) Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: goharbor#18044 Signed-off-by: chlins <[email protected]> Signed-off-by: Wilfred Almeida <[email protected]>
WilfredAlmeida
pushed a commit
to WilfredAlmeida/harbor
that referenced
this issue
Jul 8, 2023
) Fix the scanAll cannot be stopped in case of large number of artifacts, add the checkpoint before submit scan tasks, mark the scanAll stopped flag in the redis. Fixes: goharbor#18044 Signed-off-by: chlins <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How can we help you?
The jobs still be enqueued to the jobservice, and the success job numbers keep increasing which not reasonable.
The text was updated successfully, but these errors were encountered: