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

"Failed to import project" error is not clear #1757

Closed
Serhioromano opened this issue Oct 14, 2015 · 13 comments
Closed

"Failed to import project" error is not clear #1757

Serhioromano opened this issue Oct 14, 2015 · 13 comments
Labels
Improvement Minor improvement to code Needed: patch A pull request is required

Comments

@Serhioromano
Copy link

I set up everything like it is in docs and on screencast. I use Bitbacket. I push my docs that are built locally no problems to bitbuket. It is public repo I can see source as public user. I set up Service hook as well, but even if I trigger build manually it always gives me this error

2015-10-14_15-04-53

I read FAQ but I am not sure i understand if suggestion

If you see ImportError messages for custom Python modules, you should enable the virtualenv feature in the Admin page of your project, which will install your project into a virtualenv, and allow you to specify a requirements.txt file for your project.

is correct for my case. And anyway there is not link to read about requirements.txt configuration and how to configure it.

@agjohnson agjohnson added the Support Support question label Oct 19, 2015
@agjohnson
Copy link
Contributor

The suggestion won't help, as there is no ImportError thrown. This is failing on the initial checkout of your repository, which usually signifies a problem with the URL used for the project repo.

What's your project name?

@Serhioromano
Copy link
Author

What's your project name?

You mean in package.json?

ula-docs

@agjohnson
Copy link
Contributor

No, you're RTD project name.

@Serhioromano
Copy link
Author

Pardon? RTD?

@agjohnson
Copy link
Contributor

Your Read the Docs project name, I can't help any further without looking at the project configuration.

@Serhioromano
Copy link
Author

Unfortunately this issue was critical for me and I could not wait, so I use other solution now, but I wanted you to know for future customers.

@leoheck
Copy link

leoheck commented Nov 7, 2015

I am with the same problem. @Serhioromano, you didn't show your project configuration for @agjohnson help us. And, what you did to solve the problem? @agjohnson, which file you need to see to help me? I am new with RTD.

@reece
Copy link

reece commented Nov 9, 2015

I had this problem and the cause was a typo in the repo url. It appears that "Failed to import project" is returned for failed repo pulls. Makes sense in retrospect, but a more straightforward error message would help.

@Serhioromano
Copy link
Author

@leoheck

I am with the same problem. @Serhioromano, you didn't show your project configuration for @agjohnson help us

I had no longer that file by the time I was asked for it.

@leoheck

And, what you did to solve the problem?

I am using Mkdocs instead. Completely different solution.

@agjohnson
Copy link
Contributor

@reece I need to know the name of, or link to, your project on RTD, to be able to see your configuration

@reece
Copy link

reece commented Nov 10, 2015

@agjohnson I should have been clearer. I had the same error as the OP, but discovered that the cause was my own typo in the URL. When I fixed the typo, everything worked fine.

In my case at least, the only outstanding issue that "Failure to import project" is not as transparent as, say, "Could not clone or update repo from https://...".

While you're at it, you might offer a help message that suggests trying on the command line and including a copy-pastable command line (e.g., "git clone https://...").

@leoheck
Copy link

leoheck commented Nov 11, 2015

Very good guys! Now you solved my problem. Thank you. I put my docs folder somewhere inide a repo and I though that I should all the path in link. I was wrong. Thank you.

@agjohnson
Copy link
Contributor

@reece sorry, the above was meant to be in reply to @leoheck

agreed the messages could be clearer for this case though. i'll leave this open in case anyone wants to grab this.

@agjohnson agjohnson changed the title Error Failed to import project "Failed to import project" error is not clear Nov 11, 2015
@agjohnson agjohnson added Improvement Minor improvement to code Needed: patch A pull request is required and removed Support Support question labels Nov 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code Needed: patch A pull request is required
Projects
None yet
Development

No branches or pull requests

4 participants