Ignores the conf.py path on some builds

[lazka]

Details

• Read the Docs project URL: https://readthedocs.org/projects/quodlibet/
• Read the Docs username (if applicable): lazka

Expected Result

I've set a custom conf.py path in the advanced settings (for some years now)
I expect it to be always used to build the docs.

Actual Result

Since a week (this has happened at least 3 times now) it sometimes ignores the custom path and just uses "conf.py" which results in an empty/default documentation.

Good build: https://readthedocs.org/projects/quodlibet/builds/7472492/
Bad build: https://readthedocs.org/projects/quodlibet/builds/7473196/

[lazka]

I've done a few more rebuilds now and it seems just random, sometimes it uses the path sometimes not.

[lazka]

I've removed the fixed conf.py path from the settings now and it still randomly finds the conf.py and sometimes not.

[ericholscher]

This is happening because you have a tag named latest, which doesn't have any of your docs checked into it: https://github.com/quodlibet/quodlibet/tree/latest

I'm not sure why it's happening sporadically though.

[ericholscher]

Believe this is an outcome of our updated version handling code: #3913

I was looking at the versions in the admin, and accidentally overwrote the latest version, losing the build history (so the links above don't work). I've re-created latest properly, and am testing on my local instance to see how we can fix it.

[lazka]

This is happening because you have a tag named latest

Ah, that's a dummy tag I use for hosting binaries used by CI for the master branch. But that tag exists for some time now.

Thanks for looking into this.

[stsewd]

But that tag exists for some time now.

We update the version handling to fix another bug. So, now if rtd finds a tag/branch named stable or latest that replace to the rtd default tags (where rtd automatically creates the stable and latest version).

[stsewd]

I don't know the exact problem (I can't see the build history), but I would think this is as Eric mentions a problem with your tag. When you build docs for latest the original conf.py can't be found, when you build another version it can be found. The solution: you'll need to remove/rename the latest tag.

[lazka]

good: https://readthedocs.org/projects/quodlibet/builds/7476273/
bad: https://readthedocs.org/projects/quodlibet/builds/7480432/

I think the difference is that the good build is triggered through a settings change in the rtd UI and the other one is triggered through the "Build Version" button.

If me removing the "latest" tag on the repo doesn't hinder you from debugging this I'll rename it.

[ericholscher]

Go ahead and remove it. 👍

We can create a test repo with a latest tag to test against.

[stsewd]

@lazka I see, in the first build it builds from master and on the second it builds from the latest tag. This should only happen once. After building master the versions are refreshed and the rtd latest point to the latest tag, not to master. If the rtd latest point back to master without removing the latest tag from the repo, well that is a weird bug.

Can you confirm this is happening more than one time for latest?

[lazka]

@stsewd not sure. I'd guess changing settings clears some version cache so it builds master once again and then latest from there on like you said.

[stsewd]

Closing in favor of #4876