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.

I can't find documentation on what values you can use for cache duration.
In your examples you use cache('5 minutes'), and I have tried cache('1 week') which works well.

However, cache('1 month') doesn't seem to be valid.

It would be really nice to have an overview of all possible values :)

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

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

The docs of this function say...

Returns bool indicating whether interface is up and running.

However, on a network interface of mine which is UP but not RUNNING, this function returns true, suggesting that it only checks that the interface is UP.