This option applies only the processing of partitions as in:
  `slapos node instance --force-stop`

This option affects how `started` partition are processed:
- buildout is processed normally
- the services are stopped instead of started
- no promises are run
- no report is sent to master

See merge request nexedi/slapos.core!298

See merge request nexedi/slapos.core!310

See merge request nexedi/slapos.core!309

See merge request nexedi/slapos.core!305

   Since the alarm was removed to auto-cancel, we now use an action to cancel users invoices.

    It is the only sign of debt the user could have.

   Follow up changes done on the original commited on erp5 repository. The goal of this test is run against the full stack of slapos master.

   If we limit the processing from this alarm the production execeeds the processing, and it never reaches the end.

   The list is filtered by the services that have base_amount with an invoicing (or subcategory of invoicing).

   There isn't a reason to check more often since the computer must be 30 days w/o contact master to be considered outdated.

   This isn't a decision to be taken automatically, but a decision for the site administrator

   This is mostly written by Kiril.

See merge request nexedi/slapos.core!303

Before this commit, some slapos commands would output this warning:
```
  No handlers could be found for logger "cachecontrol.controller"
```

The affected commands included:
- slapos service list
- slapos service info
- slapos computer list
- slapos computer info
- slapos computer token
- slapos cache source

See merge request nexedi/slapos.core!306

See merge request nexedi/slapos.core!304

See merge request nexedi/slapos.core!300

Installing from a git checkout is a bad practice for production, but it's a
common thing during development. One problem I often face is that I have a
software release installed from a given revision and I want to make a small
change to the software, but not recompile everything. To achieve this, I need
to use the exact same git revision that was installed before, but most of the
time, I don't remember what revision I have been using last time I installed.

This change is about adding a buildout comment in the generated buildout.cfg
made to install the profile, with the revision that was used for installing, so
that we can re-install the same software again.

See merge request nexedi/slapos.core!302

See merge request nexedi/slapos.core!301

See https://lab.nexedi.com/nexedi/erp5/blob/1b31fcbd12ede57079851aa198aa8d9e9f70e073/bt5/erp5_web_renderjs_ui/PathTemplateItem/web_page_module/rjs_gadget_erp5_datetimefield_js.js#L281

Provider of the Software Installation is Assignee.
See nexedi/slapos.core@07c9102c

It was probably a typo in nexedi/slapos.core@b0b435ce