Thanks for the script Pedro, I'll check it out. Here's a status update. I moved default to 1.4.1 and site is behaving better now, but the master version still is "missing" the nav. Actually the nav is there, but not visible. One of the UI hacks on the website theme is to use some js to move the right sidebar to the left. Apparently this is failing. So the content is there, but just not appearing. If anyone is feeling up to troubleshooting some javascript, it's in docs/_static/js/sidebar.js - the code there is supposed to combine sidebars.
On Wed, Jun 12, 2019 at 6:53 PM Pedro Larroy <pedro.larroy.li...@gmail.com> wrote: > > Here is a dirty and hacky script that I use for bisect, it's a bit > more complex than using barebones git bisect due to our subrepos. I > would suggest you check for the menu on the documentation output to > return success or failure on the test function and it will find the > first commit in which the navbar is broken. > > On Wed, Jun 12, 2019 at 6:26 PM Pedro Larroy > <pedro.larroy.li...@gmail.com> wrote: > > > > I would suggest bisecting to find when the navbar was gone. I have a > > python script that I use for bisecting that I can offer. > > > > On Wed, Jun 12, 2019 at 10:28 AM Aaron Markham > > <aaron.s.mark...@gmail.com> wrote: > > > > > > Hi everyone, there's an issue with the navigation for master. When > > > you browse any of the API docs, the left nav is gone. > > > Here's the issue: https://github.com/apache/incubator-mxnet/issues/15200 > > > If anyone has ideas, I'd love to hear them. > > > > > > In the meantime, people browsing the docs are going to have a hard > > > time. I tested defaulting the site to 1.4.1 and this works as > > > expected. > > > > > > I propose that I switch this setting in CI causing the site to switch > > > to 1.4.1 as default until such time master is fixed. Or I can leave it > > > set to 1.4.1 and then update it to 1.5.0 when that goes out. In the > > > past several months I made a lot of progress getting the FAQs, > > > tutorials, and other info pages to default to the latest, and this > > > feature will still be in play. Visitors will only see 1.4.1 content > > > for the API docs and everything else will be the latest, greatest > > > info... which, in many ways is probably ideal. > > > > > > Thoughts/objections? > > > > > > Cheers, > > > Aaron
