-
Notifications
You must be signed in to change notification settings - Fork 3
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
gitlab.exceptions.GitlabGetError: 404: 404 Project Not Found #92
Comments
I tried it on a public repository as well and got the same issue. Below is the full error message for the public repo.
|
Hi @akshaykagarwal! gitlab2prov needs the project url (aka. https://gitlab.com/foo/bar) not the url of the remote repository (aka. https://gitlab.com/foo/bar.git). Simply remove ".git" from the url that you specified and you should be good to go. Let me know if it still doesn't work. |
Hi @cdboer , Thanks that did the trick. It is working now. I also noticed that it takes a really long time to process. Is there a way to speed it up? |
Sadly there is not. We are limited by the rate limit that the GitLab instance applies to API calls. In the future we may implement the ability to specify tokens for multiple user accounts which would amplify the amount of request we can do with each additional API token. But it is not yet clear if we are going to implement this as we are also exploring other options. |
Just a thought. But maybe the usage of the GraphQL API could speed up things!? https://docs.gitlab.com/ee/api/graphql/ |
We did test the GraphQL API a few months ago but GitLab seems to be on their toes when it comes to query wheight/complexity calculations. They do apply a limit on complexity which roughly equals the rate limit for calls to their REST API (at least for our purposes). But we can look into that again, i remember not taking too much time with testing. |
Ah okay. Thanks! Maybe this could still make a difference when analyzing a self-hosted GitLab instance. But thanks for elaborating on this aspect! |
I am trying to run gitlab2prov against a project. I have provided my access token in the yaml file along with the URL. Everytime I run gitlab2prov --config command, it takes a very long time and in the end gives the below error message
Exception handling command Fetch(url='<URL>', token='<Token>').
raise gitlab.exceptions.GitlabHttpError( gitlab.exceptions.GitlabHttpError: 404: 404 Project Not Found
The above exception was the direct cause of the following exception:
gitlab.exceptions.GitlabGetError: 404: 404 Project Not Found
I know the project exists since I can fetch it using the same token when I run Git clone command directly.
Not sure what is missing here since the PAT has all the access enabled.
Any help would be appreciated. :)
The text was updated successfully, but these errors were encountered: