Retry GitLab API requests on HTTP 409 Resource lock errors #28972
Closed
fgreinacher
started this conversation in
Suggest an Idea
Replies: 1 comment 1 reply
-
|
Sounds good |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
See issue: |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tell us more.
The GitLab API might return
HTTP 409 Resource lockin cases where an internal DB lock fails to be acquired in time, see https://gitlab.com/gitlab-org/gitlab/-/blob/443c12cf3b238385db728f03b2cdbb4f17c70292/lib/api/api.rb#L111. Those errors are usually transient and a retry is therefore worthwhile.The
python-gitlablibrary for example adding special handling for this in python-gitlab/python-gitlab#2326.What do you think about adding similar logic to Renovate's GitLab layer?
Beta Was this translation helpful? Give feedback.
All reactions