I'm having an issue where ReadTheDocs doesn't appear to be updating with new documentation files. Specifically, we added these files (everything d3 related here) but in ReadTheDocs they don't appear (see [this][4]); What I'd expect to see is this:
Here's a screenshot of the correctly built docs
Note the "Empirical D3 Wrapper" link, which is in the docs when built locally using "make html" but not evident when built on ReadTheDocs.
There aren't any errors in the build log that I can find, and I've tested building locally with an identical version of Sphinx to what ReadTheDocs uses.
I'm at a loss as to what could be causing this--Suggestions?
Related
I followed the steps per listed on their website, but my VS Code threw the following error, and when I went to the localhost it appeared as such (with no where to upload my own .rvt files)
Reference Application Local Host
VS Code error message
Note: I fixed the directory to look like this, but it still isn't showing me the upload portal to include my own .RVT file. Updated VS Code .env
I was following the directions exactly as they were laid out on the Forge Data Visualization Reference Application introduction, and it wasn't giving me the result that I needed and it didn't allow me to upload my own model. I tried to do these steps through the Mac OS Monterey Terminal as well as through the VS Code Terminal dozens of times with slightly different changes each time, and none of these worked. So instead, I downloaded iTerm2 and tried again, and it worked PERFECTLY!
I am preparing documentation using MkDocs and trying to generate the documentation using readthedocs. I followed the user guide but readthedocs does not seem to communicate with my uploaded .md files in my GitHub project. Instead of reading my docs/index.md file, the document generated by readthedocs says
This is an autogenerated index file.
Please create an index.rst or README.rst file with your own content under the root (or /docs) directory in your repository.
If you want to use another markup, choose a different builder in your settings. Check out our Getting Started Guide to become more familiar with Read the Docs.
© Copyright 2022. Revision 8d3f60c9.
Built with Sphinx using a theme provided by Read the Docs.
One possible issue is that the builder is Sphink instead of MkDocs, so I changed the document type to "MkDocs" in admin-> advanced setting->documentation type in readthedocs but this does not solve the issue.
I then followed the instruction in readthedocs about getting started with mkdocs, import documentation, and configuration files for Mkdocs to set up configuration files as well as requirements but none of them work.
It would be much appreciated if anyone could help me resolve this issue.
I further navigated to https://shaarp-single-interface.readthedocs.io/en/latest/README.html.
The structure in the link above does contain all the nav panels I want but this page no longer maintains the readthedocs theme.
SHAARP_Single-Interface
Search docs
Home
Installation and Setup
Simulation and Analytical Methods
Input Parameters
Output Results
Examples
SHAARP_Single-Interface
Docs »
404
Page not found
Built with MkDocs using a theme provided by Read the Docs.
However, if accessing the docs using "view docs" in readthedocs, it directs me to https://shaarp-single-interface.readthedocs.io/en/latest/, which does not contain any panel I have prepared.
It seems that the building process was fine but the docs will need some time (maybe 1-2 hours) to update.
A similar issue was reported. Autogenerated index file in readthedocs
I have a scalajs file, generated by sbt fastOptJS.
Google Chrome says:
Source Map detected. Associated files should be added to the file
tree. You can debug these resolved source files as regular JavaScript
files. Associated files are available via file tree or _P.
However, I only see the transcompiled code, instead of the source scalajs code. How to see the scalajs code in Chrome?
I just ran into this issue and the part that confused me is that the wording leads to to look for where Chrome is hiding the .map files, except it won't show you those. Instead, it has already rendered the data from those sourcemaps as a folder containing readable sources.
I'm not sure how you'd predict what that folder's name would be, but if you check out this SO question about the same Chrome issue (though it's about webpack vs Scala.js) you can see that all the readable sources were available in a top-level folder named "webpack", so for your project I'd look for a folder with a name like "Scala.js".
Chrome could definitely be more helpful here, but for the price I can't complain.
I have been trying to publish some documentation and can't get it to work. From what I can tell it looks to me as if readthedocs is ignoring the autosummary_generate = True directive in conf.py
I am using autosummary and it works well on my local machine, with all the individual .rst files being generated when calling make html.
When building on readthedocs everything appears to work, with no errors being thrown, but when trying to browse the documentation the links do not work. Digging a bit deeper I see this type of warnings:
/home/docs/checkouts/readthedocs.org/user_builds/libgs-ops/checkouts/latest/docs/source/index.rst:23: WARNING: failed to import libgs_ops.propagator
Since that is a file that should be generated by autosummary I am assuming the problem is, as I mentioned, that readthedocs has not generated the files.
You can experience the problem for yourselves here;
https://libgs-ops.readthedocs.io/en/latest/
See how none of the links work.
I found this thread, in which someone references a similar problem in one of the responses, but as the problem asked appears to be different I permit myself to create this new thread. As I said, autosummary works fine on my local install, just not on readthedocs.
I'm trying to get TypeScript source debugging working in Chrome, but I'm running into two specific and perhaps related problems.
The first is that the comment generated by the TypeScript/WebEssentials compiler that's supposed to identify the location of the source map file looks like this:
//sourceMappingUrl=MySourceFile.js.map
But Chrome won't read that file. It seems expect that the comment will look like this:
//# sourceMappingUrl=MySourceFile.js.map
If I manually change the comment to that, and refresh my page, then magically the references to all the .ts files show up as sources in the Chrome Developer Tools.
However, that leads to my second problem, as the files don't actually get loaded. The .ts source file that Chrome should be trying to download is http://localhost/MySourceFile.ts, but the one that it's actually trying to download is http://localhost/C:/source/web/MySourceFile.ts. That sort of makes sense, as the opening attributes of MySourceFile.js.map look like this:
{"version":3,"file":"tmp1523.tmp","sources":["C:/source/web/MySourceFile.ts"
But that obviously doesn't work with Chrome, as it interprets the source-map location to be entirely relative, and IIS (quite correctly) won't serve up any URL looking like http://localhost/C:/source/web/MySourceFile.ts.
So, with respect to these two problems, is it Chrome or the TypeScript source-map feature that's doing it wrong? And what's the recommended way of doing this?
I'm using Chrome 25.0.1323.1 dev-m, with TypeScript 0.8.1 and WebEssentials 1.8.5.
This is an issue with version 1.8.5 of Web Essentials (the version currently available from the Visual Studio Gallery). The latest nightly build (at time of writing http://madskristensen.net/custom/webessentials2012.vsix) fixes the problem and generates the map linkage correctly.