fix(api/errcode): extract enclosed error from a storage driver catch-all error
Whenever an unexpected error happens, the storage driver base client will wrap it in a catch-all error, `storagedriver.Error`. Because of it, if we get one of these errors we must extract the enclosed error before trying to identify the best HTTP status for it, otherwise this will always lead to a 500 Internal Server Error.
Loading
-
mentioned in commit 6d4f158b
-
mentioned in issue #458 (closed)
-
mentioned in merge request gitlab-org/build/CNG!767 (merged)
-
mentioned in merge request gitlab-com/gl-infra/k8s-workloads/gitlab-com!1254 (merged)
-
mentioned in merge request omnibus-gitlab!5623 (merged)
-
mentioned in merge request gitlab-com/gl-infra/k8s-workloads/gitlab-com!1258 (merged)
-
mentioned in merge request gitlab-com/gl-infra/k8s-workloads/gitlab-com!1259 (merged)
-
mentioned in merge request gitlab-org/charts/gitlab!2194 (merged)
-
mentioned in merge request gitlab-development-kit!2385 (merged)
Please register or sign in to comment