Class/Struct names missing from ReadTheDocs

[adamnovak]

If you go to http://vg.readthedocs.io/en/latest/rst/api.html#_CPPv2N2vg4NodeE which is the ReadTheDocs link for vg::Node, it just says struct where it is supposed to say struct vg::Node. This wasn't like that when I set up ReadTheDocs, and it makes the docs kind of impossible to read.

[adamnovak]

I'm trying to rebuild our docs on a movable branch so I can see why the RtD build produces no class names and my local build produces class names. But on RtD our pranch lust isn't updating and our "versions" page for the project returns an error.

I think this is related to readthedocs/readthedocs.org#1617 and readthedocs/readthedocs.org#1822, because @ekg pushed a branch with a non-ASCII ❤️ in it. It seems that after projects do that, they corrupt the internal state on ReadTheDocs's servers, and even after deleting the offending branch, ReadTheDocs won't work properly again.

I'm going to delete the offending branch and then see if I can do something to fix ReadTheDocs. We might have to get in contact with their developers and convince them to manually fix our project.

[ekg]

Oh no, sorry about the ❤️...

…

On Tue, Feb 7, 2017 at 7:18 PM Adam Novak ***@***.***> wrote: I'm trying to rebuild our docs on a movable branch so I can see why the RtD build produces no class names and my local build produces class names. But on RtD our pranch lust isn't updating and our "versions" page for the project returns an error. I think this is related to readthedocs/readthedocs.org#1617 <readthedocs/readthedocs.org#1617> and readthedocs/readthedocs.org#1822 <readthedocs/readthedocs.org#1822>, because @ekg <https://github.com/ekg> pushed a branch with a non-ASCII ❤️ in it. It seems that after projects do that, they corrupt the internal state on ReadTheDocs's servers, and even after deleting the offending branch, ReadTheDocs won't work properly again. I'm going to delete the offending branch and then see if I can do something to fix ReadTheDocs. We migth have to get in contact with their developers and convince them to manually fix our project. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#631 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAI4EWhcuoxjddwEvjeoGAOC9CfM-Y_2ks5raLV7gaJpZM4LofR-> .