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

As discussed in #3926, the following files do not have .py extensions because TensorFlow does not yet support the current Python.

• dynamic_programming/k_means_clustering_tensorflow.py_tf
• machine_learning/lstm/lstm_prediction.py_tf
• neural_network/gan.py_tf
• neural_network/input_data.py_tf

TODO: Restore the .py file extensions

(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.

🐛 Bug

The two bullet points don't render as bullet points.

https://pytorch.org/docs/master/autograd.html?highlight=anomaly#torch.autograd.detect_anomaly

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @so

Describe the issue linked to the documentation

The link function used in PoissonRegressor and GammaRegressor is not documented in the docstrings. They both use the log-link.

Screenshot

Description

The rich tooltip text renders in a table that is inside a parent div that has the max-width set. If the text in the table is too wide, then the text will render outside of the div.

This is being caused by this line

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

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pandas.

• (optional) I have confirmed this bug exists on the master branch of pandas.

Note: Please read this guide detailing how to provide the necessary information for us

In all of our current uses of os.umask or filesystem.umask, we always temporarily set it to a different value and then restore it using a try/finally block. I expect this pattern to continue.

Because of that, why don't we create a simple function in certbot.util that can be used as a context manager to set umask to a value and restore it to its previous value when exiting the with blo