project.protectedbranches.delete 404: 404 Not found #2536
-
|
I have a script I've written that creates/configures a gitlab project. After creating the project, the script does a "project.protectedbranches.delete('work')". 'work' is our default branch so it will always exist and is a protected branch. About half the time I make this call, I get the following callback. Is there some server/client timing that I need to be aware of? If so, is there a way to query to know that it is safe to delete the protections? Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): python: 3.7.9 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hey @jalanh11640! It's hard to say without seeing your code. But yes, GitLab does a lot of things asynchronously these days, which can take some time especially with things like creating the initial repository, branches, merge requests etc. Try with a simple sleep first, maybe a few seconds, and if that works you can then do it in a smarter loop until success or so. There's no harm in just putting this into try/except blocks until the resource is available to make requests against. It'll be fewer API calls than trying to query the state of the project. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that's not a particularly satisfying answer, but I appreciate the answer. I've updated my code to do this.. and it seems to work fine. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
@jalanh11640 there is nothing python-gitlab can do about this - you'd hit this issue with any other API client or curl as well. It may be better to open an issue upstream on GitLab if you think the error messages returned from the server are not informative enough, we really just make requests against the server. Glad you got it to work! |
Beta Was this translation helpful? Give feedback.
Hey @jalanh11640! It's hard to say without seeing your code.
But yes, GitLab does a lot of things asynchronously these days, which can take some time especially with things like creating the initial repository, branches, merge requests etc. Try with a simple sleep first, maybe a few seconds, and if that works you can then do it in a smarter loop until success or so.
There's no harm in just putting this into try/except blocks until the resource is available to make requests against. It'll be fewer API calls than trying to query the state of the project.