A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

Environment

• Package version(s): @blueprintjs/core ^3.22.3
• Browser and OS versions: Mac OS X Chrome 79.0.3945.88

If possible, link to a minimal repro (fork this code sandbox):

Steps to reproduce

Spotted this while building a <ControlGroup> that contained buttons, selects, and some dividers.

`

Description

This utility can monitor open files number count (in real-time)?

Example count open files in the Linux machine, and count open files group by existing users.

Versions

Nothing

Logs

Nothing

Live CDs/USBs, netbooted PCs and in some cases discardable VMs and containers, usually have a read only base image and an overlayfs/tmpfs/cow filesystem on top of them.

There, we want some services not to run, like package manager upgrades, certain cron-like jobs etc.

It would be awesome if upstream systemd documented what "constitutes a live mode", e.g. the presence of a /run/live directory

It would be really useful if the project would have a bindep.txt file which mentions system packages required for building the code.

Details at https://docs.openstack.org/infra/bindep/readme.html -- I mention that there is nothing specific to OpenStack about bindep tool.

386 can't use strace

In the code sample below, taken from the Integration page on the wiki,

  #define LOG_PAGE_SIZE       256
  
  static u8_t spiffs_work_buf[LOG_PAGE_SIZE*2];
  static u8_t spiffs_fds[32*4];
  static u8_t spiffs_cache_buf[(LOG_PAGE_SIZE+32)*4];

could the magic numbers be clarified?

For spiffs_work_buf, this is because SPIFFS needs at least 2 pages for doing it's magic, cor

https://www.usenix.org/conference/opml19/program

Prepare to read papers

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

The documentation should be extended to reflect the included methods of "IEnumerableSignatures" in the section of

https://github.com/StefH/System.Linq.Dynamic.Core/wiki/Dynamic-Expressions#sequence-operators