fix(gc): commit database transaction when no task was found
Previously the workers were rolling back the database transaction in this scenario which is wrong and causes an unnecessary alert if aborted transactions are being monitored on the database server side.
Loading
-
mentioned in commit 1d19a4b6
-
mentioned in merge request gitlab-org/build/CNG!815 (merged)
-
mentioned in merge request gitlab-com/gl-infra/k8s-workloads/gitlab-com!1331 (merged)
-
mentioned in merge request gitlab-com/gl-infra/k8s-workloads/gitlab-com!1333 (merged)
-
mentioned in merge request gitlab-org/charts/gitlab!2257 (merged)
-
mentioned in merge request omnibus-gitlab!5727 (merged)
-
mentioned in merge request gitlab-development-kit!2385 (merged)
Please register or sign in to comment