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

System information

• TensorFlow version (you are using): 2.1
• Are you willing to contribute it (Yes/No): No

Project Euler has about 700 problems, but the current repository hosts solutions for only about 60-70 problems.
I'm willing to work on the issue and also if someone wants to help they can join in.
We can create guidelines on how many minimum solutions a PR should have to prevent spammy PRs with just one or two easy solutions. (open to discussion)

(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

Compiling against the C++ API on macOS using GCC-9.3, and cmake seems to use a bad flag:
... -fopenmp -D_GLIBCXX_USE_CXX11_ABI= -std=c++14 ... -- note how it "blanks out" the _GLIBCXX_USE_CXX11_ABI variable. This causes the compiler to fail in the stdlib:

/usr/local/Cellar/gcc@9/9.3.0/include/c++/9.3.0/x86_64-apple-darwin18/bits/c++config.h:273:27: error: #if with no expr

Describe the issue linked to the documentation

Follows from #17387

Suggest a potential alternative/fix

Stop referencing preprocessing functions e.g. :

maxabs_scale
minmax_scale
normalize
quantile_transform
robust_scale
scale
power_transform

in the UG, and only add them e.g. in the "See Also" sections, or even just in the API ref.

In particular right now the first entr

Summary

Usage of HttpCompressionMiddleware needs to be relfected in Scrapy stats.

Motivation

In order to estimate scrapy memory usage efficiency and prevent.. memory leaks like this.
I will need to know:

1. number of request/response objects that can be active (can be achieved by using [trackref](https://docs.scrapy.org/en/latest/topi

Is your feature request related to a problem? Please describe.
I have a lot of trouble distinguishing between the shades of green signifying a running vs successful query in sqllab.

Describe the solution you'd like
Ideally these would be two different colors for running vs successful. Maybe yellow and green respectively?

Describe alternatives you've considered
If there isn't

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?

Location of the documentation

https://pandas.pydata.org/docs/dev/reference/api/pandas.Timestamp.strftime.html?highlight=strftime#pandas.Timestamp.strftime

Documentation problem

The argument for TimeStamp.strftime() is missing in the docs

Suggested fix for documentation

Argument is a format string. Should reference python docs https://docs.python.org/3/library/datet