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.

Documentation fixes

See original GitHub issue

Update Sklearn intersphinx, and make it the stable version instead of dev
Fix the build warnings:

11:02:00 AM: /opt/build/repo/graspy/cluster/gclust.py:docstring of graspy.cluster.GaussianCluster:35: WARNING: Bullet list ends without a blank line; unexpected unindent.
11:02:00 AM: /opt/build/repo/graspy/cluster/gclust.py:docstring of graspy.cluster.GaussianCluster:56: WARNING: Unexpected indentation.
11:02:00 AM: /opt/build/repo/graspy/embed/svd.py:docstring of graspy.embed.select_dimension:51: WARNING: Footnote [#] is not referenced.
11:02:00 AM: /opt/build/repo/graspy/inference/latent_position_test.py:docstring of graspy.inference.LatentPositionTest:37: WARNING: Explicit markup ends without a blank line; unexpected unindent.
11:02:00 AM: /opt/build/repo/graspy/inference/latent_position_test.py:docstring of graspy.inference.LatentPositionTest:40: WARNING: Explicit markup ends without a blank line; unexpected unindent.
11:02:00 AM: /opt/build/repo/graspy/inference/latent_position_test.py:docstring of graspy.inference.LatentPositionTest:64: WARNING: Unknown target name: "p_value_1".
11:02:00 AM: /opt/build/repo/graspy/inference/latent_position_test.py:docstring of graspy.inference.LatentPositionTest:64: WARNING: Unknown target name: "p_value_2".
11:02:00 AM: /opt/build/repo/docs/reference/utils.rst:28: WARNING: Unknown directive type "autofumction".
11:02:00 AM: .. autofumction:: get_multigraph_intersect_lcc
11:00:20 AM: intersphinx inventory has moved: http://scikit-learn.org/dev/objects.inv -> https://scikit-learn.org/dev/objects.inv

Issue Analytics

State:
Created 4 years ago
Comments:39

Top GitHub Comments

1reaction

bdpedigocommented, Sep 7, 2020

No need to make a new PR. If you update your branch and push, the PR will update as well

1reaction

pauladkissoncommented, Sep 6, 2020

I used git in a couple small 3-5 person projects just last semester, and I did the tutorial before starting class. But I am still getting used to the ins and outs. For example, on my projects before we used branches but not forks, so that part was a little confusing, but reading the contribution guidelines helped clear things up.

For my install, I used pip install graspy from within the graspy folder.

Thanks @bdpedigo! I’m just making sure that I follow all the contributing guidelines and then I’ll submit my PR!

Top Results From Across the Web

Template: Bug Fixes Documentation List - OpenRegulatory

This list is used to document the evaluation and implementation of all bug fixes according to the company's change management process. Documentation of...

Fixing your Documentation Problem - DEV Community ‍ ‍

The Solutions. The Pains. If you've worked on any project that is not 100% your own making, you've had plenty of problems due...

How do we fix the state of technical documentation?

The answer comes in several degrees of intervention. The first and most obvious is to hire a professional to take care of it....

Known Issues, Bug Fixes, and Documentation Issues

This chapter contains information about known issues, bug fixes, and documentation issues for Oracle Secure Global Desktop (SGD).

Does documentation and fixing belong in the Product Backlog?

The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product ...