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

Error: An unexpected error occurred #2985

Closed
tannerjfco opened this issue Jun 30, 2017 · 21 comments
Closed

Error: An unexpected error occurred #2985

tannerjfco opened this issue Jun 30, 2017 · 21 comments
Labels
Bug A bug

Comments

@tannerjfco
Copy link

Details

We were initially getting build failures over a configuration issue. I believed to have resolved the configuration, but there's no way to tell with the error message provided. The build linked above is from a Version I added against a branch, which is rolled back to our last known good commit for readthedocs, so it should succeed. It fails, and at this point I don't seem to have any way to successfully build my docs.

Expected Result

Either:

  • The build succeeds
  • The build fails, and provides me a useful error message that tells me something about the error and ideally how to resolve it.

Actual Result

The build failed with the following: "Error: an unexpected error occurred". This error message gives me nothing to work with. I can't imagine its all that useful to a developer reading reports like this either. Searching the web for this issue is also useless, since every previous report is either a case that readthedocs devs identified as some problem that's reported as solved, or some user magically figuring out their issue was some configuration issue not relevant to my project.

@smsullivan
Copy link

Hitting this issue as well, but I just checked my latest public build and the updated docs are actually showing up correctly. So even though it is telling me I have a failed build (with the "unexpected error occurred" message), the docs are actually building and showing up.

@marcelstoer
Copy link
Contributor

Dup of #2982

@mepi0011
Copy link

mepi0011 commented Jul 2, 2017

Get the same on my project.

https://readthedocs.org/projects/openhabdoc/builds/5634911/

@trpedersen
Copy link

I have the same problem; builds are reporting as failed, but the updated docs are being installed. It seems something fails after the 'Installing' step.

Example build URL: https://readthedocs.org/projects/uhack-guide/builds/5635512/
Project: https://readthedocs.org/projects/uhack-guide/

@MaslovaEV
Copy link

MaslovaEV commented Jul 5, 2017

I have been facing this issue since the past week(( so the documentation on my project can not be updated...

UPD: Today it works ok for my project! Thanks!
But the same documentation from a different git repo fails with an undefined error https://readthedocs.org/projects/stream-juggler/builds/5651727/

UPD2: Now it works ok! Thanks again!

@weitzman
Copy link

weitzman commented Jul 5, 2017

Same here. Builds are showing new HTML but reporting as failed:

Example Build URL: https://readthedocs.org/projects/drush/builds/5646326/

@trpedersen
Copy link

I tried creating a new project (from the same source repo in Bitbucket), to no avail - builds still report 'unexpected error' but the HTML is built successfully.

Eg: https://readthedocs.org/projects/uhack-guide-2017/builds/

@byjg
Copy link

byjg commented Jul 5, 2017

Mine project failed and the HTML document is not created. http://yaj.readthedocs.io/en/latest/

@agjohnson
Copy link
Contributor

I believe this is a problem with unicode that was introduced with either changes for py2/3 compatibility or recent changes to our file syncing code.

@agjohnson
Copy link
Contributor

Yup, underlying it is an issue with YAML and unicode. Fix at #2998

@byjg
Copy link

byjg commented Jul 11, 2017

Build still failing:

Build #5673116
latest (dbb7515474cb300bb884d318c084d12d9e41543b)
Build failed
Erro

An unexpected error occurred
python2.7 -mvirtualenv --no-site-packages --no-download /home/docs/checkouts/readthedocs.org/user_builds/yaj/envs/latest
python /home/docs/checkouts/readthedocs.org/user_builds/yaj/envs/latest/bin/pip install --use-wheel -U --cache-dir /home/docs/checkouts/readthedocs.org/user_builds/yaj/.cache/pip sphinx==1.5.3 Pygments==2.2.0 setuptools==28.8.0 docutils==0.13.1 mkdocs==0.15.0 mock==1.0.1 pillow==2.6.1 readthedocs-sphinx-ext<0.6 sphinx-rtd-theme<0.3 alabaster>=0.7,<0.8,!=0.7.5 commonmark==0.5.4 recommonmark==0.4.0
python /home/docs/checkouts/readthedocs.org/user_builds/yaj/envs/latest/bin/mkdocs build --clean --site-dir _build/html --theme readthedocs

@martindevans
Copy link

I also have this problem.

Build: https://readthedocs.org/projects/dissonance/builds/5688334/
Docs: https://dissonance.readthedocs.io/en/latest/

As others have said, the build reports a failure but the live version of the docs appears to be up to date.

@ethernomad
Copy link

https://readthedocs.org/projects/link-blockchain/builds/5713802/

python2.7 -mvirtualenv --no-site-packages --no-download /home/docs/checkouts/readthedocs.org/user_builds/link-blockchain/envs/latest
 New python executable in /home/docs/checkouts/readthedocs.org/user_builds/link-blockchain/envs/latest/bin/python2.7
Also creating executable in /home/docs/checkouts/readthedocs.org/user_builds/link-blockchain/envs/latest/bin/python
Installing setuptools, pip, wheel...done.

@smsullivan
Copy link

The issue seems to be resolved. My project started building successfully a day ago (7/20/2017) and it seems many of the projects here are building successfully as well now.

@hyt-hz
Copy link

hyt-hz commented Jul 27, 2017

same problem here, it only says "An unexpected error occurred", don't know what to do:

https://readthedocs.org/projects/ivr/builds/5749015/

@azhipaigor
Copy link

Same problem: "An unexpected error occurred"
Build: https://readthedocs.org/projects/diadocsdk-1c/builds/5852205/

@decentral1se
Copy link
Contributor

decentral1se commented Aug 23, 2017

Also seeing this one https://readthedocs.org/projects/stack/builds/5876544/.

It would be much nicer to see a stack trace here instead of 'unexpected error'.

@decentral1se
Copy link
Contributor

Coming back to this, I see that we're both (the OP and I) complaining about this bad error message. Maybe I should just do something about fixing this myself instead of moaning :) Can any core dev seeing this perhaps point me in the right direction and I'd definitely take a stab at exposing the real error messages.

@agjohnson
Copy link
Contributor

I addressed this a bit in #3073. A hotfix is out, folks can test their builds again to be sure.

@ericholscher
Copy link
Member

This should be fixed, as this error was previously a generic one we threw, but now have fixed.

@decentral1se
Copy link
Contributor

Thank you all!

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

No branches or pull requests