ahmido
1fec9c6f9d
Some checks failed
Main Confidence / confidence (push) Failing after 45s
## Summary - introduce surface-aware compressed governance outcomes and reuse the shared truth/explanation seams for operator-first summaries - apply the compressed outcome hierarchy across baseline, evidence, review, review-pack, canonical review/evidence, and artifact-oriented operation-run surfaces - expand spec 214 fixtures and Pest coverage, and fix tenant-panel route assertions by generating explicit tenant-panel URLs in the affected Filament tests ## Validation - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - focused governance compression suite from `specs/214-governance-outcome-compression/quickstart.md` passed (`68` tests, `445` assertions) - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/InventoryItemResourceTest.php tests/Feature/Filament/BackupSetUiEnforcementTest.php tests/Feature/Filament/RestoreRunUiEnforcementTest.php` passed (`18` tests, `81` assertions) Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #253
39 lines
1.4 KiB
Plaintext
39 lines
1.4 KiB
Plaintext
# Restarting Commands
|
|
|
|
Sometimes it's useful to have commands that exited with a non-zero status to restart automatically.<br/>
|
|
concurrently lets you configure how many times you wish for such a command to restart through the `--restart-tries` flag:
|
|
|
|
```bash
|
|
$ concurrently --restart-tries 2 'exit 1'
|
|
[0] exit 1 exited with code 1
|
|
[0] exit 1 restarted
|
|
[0] exit 1 exited with code 1
|
|
[0] exit 1 restarted
|
|
[0] exit 1 exited with code 1
|
|
```
|
|
|
|
Sometimes, it might be interesting to have commands wait before restarting.<br/>
|
|
To do this, simply set `--restart-after` to a the number of milliseconds you'd like to delay restarting.
|
|
|
|
```bash
|
|
$ concurrently -p time --restart-tries 1 --restart-after 3000 'exit 1'
|
|
[2024-09-01 23:43:55.871] exit 1 exited with code 1
|
|
[2024-09-01 23:43:58.874] exit 1 restarted
|
|
[2024-09-01 23:43:58.891] exit 1 exited with code 1
|
|
```
|
|
|
|
If a command is not having success spawning, you might want to instead apply an exponential back-off.<br/>
|
|
Set `--restart-after exponential` to have commands respawn with a `2^N` seconds delay.
|
|
|
|
```bash
|
|
$ concurrently -p time --restart-tries 3 --restart-after exponential 'exit 1'
|
|
|
|
[2024-09-01 23:49:01.124] exit 1 exited with code 1
|
|
[2024-09-01 23:49:02.127] exit 1 restarted
|
|
[2024-09-01 23:49:02.139] exit 1 exited with code 1
|
|
[2024-09-01 23:49:04.141] exit 1 restarted
|
|
[2024-09-01 23:49:04.157] exit 1 exited with code 1
|
|
[2024-09-01 23:49:08.158] exit 1 restarted
|
|
[2024-09-01 23:49:08.174] exit 1 exited with code 1
|
|
```
|