Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions deploy/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@

## Unreleased

- Safe mode counts every start as failed from its first moments until it stays up 5 minutes or shuts down in order, so starts that end in a power cut, a reset or a hang count too, and so does a crash restart up to 5 minutes into a start (the crash handler restarts the head unit about a minute and a half after a crash). Three failed starts in a row turn it on, and the start that follows already runs without our tools: their units start after the guard's first step. A `systemctl reboot` or `poweroff` counts as an orderly shutdown.
- An install cut short between moving a tool's version folder aside and putting the new one in its place gets the folder back at the deploy tool's next install or other change.

## 0.8.25

- `uninstall` refuses to remove a component that an installed app or tool still depends on (its requirements, or a capability only that component provides), and names those components. Remove them first, or use `remove-all`, which removes them in order.
Expand Down
16 changes: 10 additions & 6 deletions deploy/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -576,12 +576,16 @@ services it installed stay.

### Safe mode

When the head unit restarts four times in a row within 2 minutes of
starting, by a crash or recovery restart none of our tools asked for, our
tools' units stay off from the next start: **safe mode**. BMW's units are
never touched. Units marked `"runsInSafeMode": true` in their tool's
`component.json` still run; give it to units that recover the head unit or
leave safe mode:
When three starts of the head unit end within 5 minutes, by a crash or
recovery restart none of our tools asked for or with no orderly shutdown
at all (a power cut, a reset), and no start between them stays up 5
minutes, our tools' units stay off from the next start: **safe mode**. The
guard runs first at each start and our tools' units start after it, so the
start that follows the third failed one already runs without them. A
shutdown in order (switching the car off, the Store's or the HMI's
restart) never counts. BMW's units are never touched. Units marked
`"runsInSafeMode": true` in their tool's `component.json` still run; give
it to units that recover the head unit or leave safe mode:

```json
"units": [{ "name": "acme-recovery.service", "from": "systemd/acme-recovery.service", "runsInSafeMode": true }]
Expand Down
Loading