Please make sure that this is a documentation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:doc_template

System information

• TensorFlow version: 1.13.1
• Doc Link: https://www.tensorflow.org/api_docs/python/tf/cus

I have a simple instruction which is good to be kept in CONTRIBUTION.md. Please add this wherever it looks good:

• clone your forked repository locally
• change directory to its root
• run pip install pre-commit
• run pre-commit run --all-files
• commit and push the changes to your fork.

(e.g. for links and images), because some of these examples are now being rendered in the docs.

Added by @fchollet in requests for contributions.

It should be added to the .rst so that they appear on the website.
Doc is already inline here https://github.com/pytorch/pytorch/blob/df88cc3f7f5c13221a93d7d3d38e681a3d5a6b6a/torch/nn/modules/module.py#L89-L115

cc @jlin27 @mruberry

Most functions in scipy.linalg functions (e.g. svd, qr, eig, eigh, pinv, pinv2 ...) have a default kwarg check_finite=True that we typically leave to the default value in scikit-learn.

As we already validate the input data for most estimators in scikit-learn, this check is redundant and can cause significant overhead, especially at predict / transform time. We should probably a

Some of the links like cryptography installation in file install.rst are outdated and require an update.
It will be nice to check for other parts of the documentation for the same issue.

Expected results

Layer type resets to default

Actual results

The entire page goes blank

Screenshots

![image](https://user-images.githubusercontent.com/8

Hello everyone, I will explain the current status of manim in this issue.

Now there are three main manim versions, and their differences:

1. The master branch of 3b1b/manim: (probably the most used currently) rendering on the CPU using cairo, currently stable.
2. The shaders branch of 3b1b/manim: (Grant is making, usi

Copied from #7991:

If you look at https://certbot.eff.org/docs/api/certbot.compat.filesystem.html, you'll notice many formatting errors which should be fixed.

That's the bare minimum which I think should be done, but I think we should also see what we can do to avoid these problems from happening in the future. Is there a way we could build the docs in CI and check for these problems?

pd.testing.assert_series_equal(result, expected)

should fail style checks, rather we want tm.assert_series_equal

we need to update any usages in the codebase as well as add this to the pre-commit checks.