[BUG] exo run doesn't make clear when a process doesn't start
BenElgar opened this issue · comments
At the moment it's very unclear that a process has failed to start. In the scenario below the web component failed to start but exo run happily continued to printing logs for the postgres component without emitting an error message. My ideal would be that exo run halts if a process fails to start.
❯ exo run
GUI available at: http://localhost:4001/#/workspaces/f2nsw260w3f2gm26190hnv0k8g
Job URL: http://localhost:4001/#/jobs/2z9y3rfj0vqgjq22veh37anx2c
applying
⨯ ├─ deleting web cannot find workspace for component "hn6z8vhrvjfcyjba4eccagy30g"
✓ ├─ deleting db
✓ ├─ deleting postgres-data
✓ ├─ re-creating postgres-data
✓ ├─ deleting postgres
✓ ├─ re-creating postgres
⨯ ├─ deleting default cannot find workspace for component "hn6z8vhrvjfcyjba4eccagy30g"
✓ └─ re-creating default
18:22:51 web Response 18:22:51 web Response {{
*** 500 lines of log output for the previous three days ***
18:36:01 web event - compiled successfully
11:54:26 EXO applying manifest... j4rtxwvhhgfkr68nrkttj0d18g
11:55:23 EXO applying manifest... 60n6396fmc8tprmgxejgsdqge8
12:00:24 EXO applying manifest... s3aj835dhxmv6fczvhkmjc57ar
12:03:00 EXO applying manifest... 3npy8kqdrwkfj32v9ktk3v5m50
12:03:30 EXO applying manifest... xy8wdtqv3qrwjwemea906e7a9c
12:04:06 EXO stopping...
12:04:07 EXO applying manifest... 2zped2nyb46r92razywm1n70am
12:04:36 EXO stopping...
12:04:39 EXO applying manifest... 7aha8h2ppk97bt3sgz1kswb7v8
12:04:51 EXO stopping...
12:04:57 EXO applying manifest... 2z9y3rfj0vqgjq22veh37anx2c
13:04:57 postgres PostgreSQL Database directory appears to contain a database; Skipping initialization
13:04:57 postgres 2021-10-01 11:04:57.828 UTC [1] LOG: starting PostgreSQL 12.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
13:04:57 postgres 2021-10-01 11:04:57.828 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
13:04:57 postgres 2021-10-01 11:04:57.828 UTC [1] LOG: listening on IPv6 address "::", port 5432
13:04:57 postgres 2021-10-01 11:04:57.832 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
13:04:57 postgres 2021-10-01 11:04:57.846 UTC [21] LOG: database system was shut down at 2021-10-01 11:04:51 UTC
13:04:57 postgres 2021-10-01 11:04:57.849 UTC [1] LOG: database system is ready to accept connections
Never mind, sorry, this was because exo run was running the docker compose file rather than the procfile that I was expecting it to.