Skip to content
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

404 on org-sync-import gitlab project #45

Closed
alvaroabascar opened this issue Jun 26, 2018 · 5 comments
Closed

404 on org-sync-import gitlab project #45

alvaroabascar opened this issue Jun 26, 2018 · 5 comments

Comments

@alvaroabascar
Copy link

After reading through the issues I see @plajjan developed the gitlab backend. I'm experiencing the following issue:

After running org-sync-import and entering the URL of a gitlab project (with format https://gitlab.com/group/project), import fails with Wrong type argument: listp, "404 Project Not Found". This happens both with public and private repos. ¿Am I doing something wrong or is the backend broken?

I'm using the master branch of org-sync, commit '095335063b30687'.

Thanks!

@plajjan
Copy link
Collaborator

plajjan commented Aug 3, 2018

FYI, I'm on parental leave which is why I haven't seen this until now and why I won't be looking into it for at least another month or so ;)

Also, @yisraeldov and @To1ne worked on the foundation for the gitlab backend. I only added on top (and managed to get commit rights in the process).

@plajjan
Copy link
Collaborator

plajjan commented Aug 3, 2018

But just looking at the error message, it seems we don't properly catch some error, like we expect something to get returned but instead get a 404 error message. We should probably throw an error earlier...

@divansantana
Copy link

FYI, I'm on parental leave which is why I haven't seen this until now and why I won't be looking into it for at least another month or so ;)

Ah that explains a lot of why activity has slowed down. Congrats and good luck.

@WhatisRT
Copy link

WhatisRT commented Oct 2, 2018

I got the same issue, which was caused by using the URL that used 'issues' at the end. I removed that and it worked. This should probably be documented somewhere.

@plajjan
Copy link
Collaborator

plajjan commented Dec 4, 2018

I updated the documentation in the header of the gitlab file in #47 as per @WhatisRT suggestion. Assuming that his analysis of this issue is correct, the problem is now fixed. Given that OP @alvaroabascar hasn't updated the issue in anyway I consider it abandoned but with a probable correct answer, thus closing :)

If not, feel free to reopen or open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants