-
Notifications
You must be signed in to change notification settings - Fork 69
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 load config for /refs/... from ... No matching refs found #86
Comments
@mamueluth I have the same problem, but a project which worked fine a few days ago does not work anymore. Can you verify the previous project still works for you? What environment are you running in? |
In my case the issue was that I called |
I've a similar problem
Other versions start. This is invoking from within
Not |
I think I might have found the source of my problem. The version = "" It was only prior to the release of v0.3.0 that I implemented automatic version control (first with versioneer then switched to setuptools_scm). I wonder if the lack of explicit version is why the build with Is there anyway to work around or fix this? New commits to add the version wouldn't align with the tagged commits I guess the tags could be moved perhaps but am unsure if that is wise ( |
If conf.py or its subsidiary code e.g extension for any ref (branch, tag, ) that you want to create documentation for is broken, then such error might occur. I knew what happened by debugging exception in load_sphinx_config_worker function in main.py of sphinx_multiversion package (https://github.com/Holzhaus/sphinx-multiversion/blob/cdc9cb591a738e67a5aacc458f9c95e2b88a94c2/sphinx_multiversion/main.py#L73). |
Duplicate of #17 |
Hi there.
I have used sphinx-multiversion successfully for another project. However, if I use my slightly adjusted
conf.py
for the current project I get the following error:This error appears no matter what branches I whitelist. Building with
sphinx-build
itself however works fine. If someone could hint me in the right direction what could lead to this behavior, I would be thankful.The text was updated successfully, but these errors were encountered: