Documentation bugs
See original GitHub issueThis is a running list of bugs I’ve noticed in the documentation that need to be fixed.
- Sections don’t have permalinks
- “Open in Colab” button is too wide: https://github.com/pytorch/pytorch_sphinx_theme/issues/140, https://github.com/pytorch/pytorch_sphinx_theme/pull/142
- Fonts are missing, requiring hack to
requirements.txt
: https://github.com/pytorch/pytorch_sphinx_theme/issues/143 - Dataset base class is incorrect: https://github.com/sphinx-doc/sphinx/issues/9607
- Models and trainers are missing args/returns documentation
- Tutorials don’t run on Colab, need to clone from GitHub and install dependencies (or pip install once we release on PyPI)
- Notes on how to download SEN12MS and So2Sat aren’t showing up (https://github.com/microsoft/torchgeo/commit/3d3b903d94c9ada2f9e0e919f254d7a8406d7e25, https://github.com/microsoft/torchgeo/commit/fd4998b78737aad6924a7d67c912f01661f96839)
- API docs show “Return type: None” for most functions, see if we can get rid of this (#277)
- In-line code missing off-color background (https://github.com/pytorch/pytorch_sphinx_theme/issues/130)
- the “well-tested” and “linters” links are broken on the users/contributing page (6d5725056c2c7851e2dc9a47952e2cd884ed43a4)
- NAIP has no docs because docstrings aren’t inherited from parent classes
- BoundingBox docs aren’t formatted correctly: https://torchgeo.readthedocs.io/en/latest/api/datasets.html#torchgeo.datasets.BoundingBox
- Nested lists have a lot of unnecessary whitespace
- Models have extra undocumented
parameters
defined - Trainer kwargs are showing up under
parameters
- Versions popup menu appears on wrong side of the screen
- Versions popup menu does not have release versions, only latest and stable
-
__getitem__
is showing up before__init__
because things are sorted alphabetically, we don’t want this -
torchgeo.samplers.Units
: possible enum values not displayed -
torchgeo.datasets.RasterDataset
: class attributes not displayed
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Documentation bugs
Bug triaging is the process of reviewing new bugs, verifying whether a bug is valid or not, and gathering more information about it....
Read more >Reporting Documentation Bugs - MariaDB Knowledge Base
This page contains general guidelines for the community for reporting documentation bugs. Known Bugs. First, check that the bug isn't already filed in...
Read more >Common word bugs in software documentation and how to fix ...
Common word bugs in software documentation and how to fix them · Use Correct Words · Go forth and write docs.
Read more >Dealing with Bugs — Python 3.11.1 documentation
It can be sometimes faster to fix bugs yourself and contribute patches to ... A list of documentation bugs that have been submitted...
Read more >How to Write A Good Bug Report? Tips and Tricks
There is no doubt that your bug report should be a high-quality document. Focus on writing good bug reports and spend some time...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the catch / report @robmarkcole! This is one of the few things that isn’t tested… Fixed in #434
There is an error in
trainers.ipynb
. The csv is created with upper case column names (e.g. train_RMSE). Cell fixed below: