Bug description
On the https://psutil.readthedocs.io/en/latest/ page, there are 'terminate my children' links to the https://psutil.readthedocs.io/en/latest/#terminate-my-children section which appears to not exist anymore.

This is not an issue in 5.3.0 (https://psutil.readthedocs.io/en/release-5.3.0/#terminate-my-children).

Consider this scenario:

My phone is connected to WiFi(4g), the power goes off, and my mobile data(2g) kicks into action. If there were multiple assets fetched for 4g, all their low quality equivalents will now be fetched.
This will also happen when I am travelling between places as my data speed keeps fluctuating.

I am not sure what the solution to this problem is but I believe we shouldn'

To describe:

• How to contribute code.
• code style
• document style
• how to test
• purpose of this project, what to do and what not to do.

http://man7.org/linux/man-pages/man3/malloc_trim.3.html

This is a GNU extension, but it seems a lot of other allocators support it as well. It would be useful to have in e.g. system wide low-memory conditions.

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Since we are adding an "Import settings" feature in 2.1, we can also create some nice ready-made settings users can simply import in the app. I would suggest we create a few and place them in a folder like "example settings" here in GitHub with preview images in the README file. Let me k

It turns out if we do app.use(cache('5 minutes')), it will cache all routes, regardless of methods like GET and POST. However, for methods like PUT and POST, in many cases this implied update on the server side and shall not be cached. Should we add documentation or functionality to make supporting such case more easily?

In addition to memory-specific concepts already described in docs, it would be useful to describe basic concepts of memory management, such as allocator, arena, pool, etc. This would make the library design easier to understand by newcomers. Also this clarifies the nomenclature used by the library and its docs.

I am a little confused on how and when to use memfs, unionfs, linkfs, patchFs, patchRequire, jest-plugin-fs etc.

There are a lot of pieces to make a great vehicle but the instructions on how assembling them together are not well organized. A lot of documentation is sparse across different repos and issues on those repos. Outdated info in old issues and changes in the state of the

E.g. search history per se is not useful perhaps, but having it around is quite convenient as a means of answering 'How did I get on this page?'.

Old bunch of the examples (removed at 7327b6d7097c5595d5121d48bd801bc016707e18) was not that good, as they were using internal APIs and worked with sub-crates directly, which led to confusion, since the intended way to work with heim is via facade crate.

Right now there is a bunch of new examples exist, but it would be nice to have more