Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
404 link to documentation
See original GitHub issue * JGraphT version: n/a
* Java version (java -version)/platform: n/a
Issue https://jgrapht.org/guide/UserOverview leads to a 404.
Steps to reproduce (small coding example)
- Go to jgrapht.org
- Scroll to Documentation section
- Click on User Guide
Expected behaviour Being able to access the documentation site.
Other information
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
404 Pages — ExpressionEngine 6 Documentation
The 404 page setting tells ExpressionEngine which template to use for all the 404 errors that are received. It is worth noting that...
Read more >Page not found - Document360
Page not found is a sub-feature under the Analytics menu of Document360. This feature shows the list of URLs for which · 404-page...
Read more >Generate 404 Not Found Pages Automatically for Sphinx Docs ...
sphinx-notfound-page is a Sphinx extension to create custom 404 pages and help you to generate proper resource links (js, css, images, etc) to...
Read more >Building a smart 404 page with Swiftype
You can find a full working example that renders smart 404 pages based on the search engine for the Swiftype documentation on GitHub....
Read more >Creating a Custom 404 Page - Unbounce documentation
You can still use your 404 page to connect with your customers and corral them back to where they need to be. The...
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 Free
Top 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
OK, fixed it by telling nvm to use node lts version. I also sprinkled in a few set -e directives so that if this happens again in the future, the build will fail instead of pushing missing docs. Should still probably lock node and hercule versions, so I’m going to create a separate issue for that.
If the docs don’t show up yet, use this link to bypass the CDN:
https://jgrapht.org/guide/UserOverview?version=xyz
Thanks for reporting!
Aaaaaand note #950