We've now gotten a fair number of "cheatsheet" entries in the books list. I'd like to propose that we move these to a separate page.

Reasons:

1. Will be easier to find cheatsheets
2. Cheatsheets aren't books
3. Cheat sheets aren't so spoken-language specific.
4. The english-language books page is getting long.
5. Will encourage better cheatsheet coverage.

Against:

1. Scope creep.

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.

https://material-ui.com/api/select/
The docs says that you cannot use empty string value for value field. As long as this is eventually acceptable, there is an issue, because for some reason null value also does not work. These both totally break my communication with backend service, because it seems I'll have to find and replace the values before saving (I do want to save null).
If I c

Proof read transcribed code of UPDATE_PROGRAM against scans

Lines: 548
Page: 1386—1396 (10)

Reduced quality scans can be found here

Actual behaviour

When simply trying to edit some additional files I often type :e *.js or something similar; this almost ALWAYS results in E77: Too many file names.

Expected behaviour

It's pretty clear what the user wants in this situation; they want to open the files as buffers! I'm sure there are legacy reasons for this error, but it's a pretty poor experience these days that

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

Environment:
Grafana 7.3
Data source: custom back-end data source, https://github.com/KeckObservatory/epics-grafana-datasource
OS: CentOS 7
User OS/browser: Chrome 83

When a combo box("Select" component) in the query parameters has many entries, clicking on it will sometimes make it pop upwards (vs downwards). The component Z order is apparently underneath the graph itself, obscuring the t

Related PR: #6331
Suggested by @pimlie

When trailing slash handling is enforced (in any manner), it'd be great to have two things for improved DX:

Nuxt Link adaption

No matter how you input the links in your Nuxt link (be it as an object via named routes or via string), the component should enforce the set up trailing slash handling (adding or removing the slashes as needed).

U