Bug: Fails to run on first start: dependency failed to start: container test-graphql-1 is unhealthy

Creating a clean project fails with an error the first time.
Though if I respond n to stop the development environment and then try again it works.
andre in Documents/scratch/test at ubuntu-vm at ☸  do-sfo3-lambdo-posthog-k8s
➜ nhost init
Initializing Nhost project
Successfully initialized Nhost project, run `nhost up` to start development

andre in Documents/scratch/test at ubuntu-vm at ☸  do-sfo3-lambdo-posthog-k8s took 5s
➜ nhost up
Setting up Nhost development environment...
Starting Nhost development environment...
[+] Running 12/13
 ⠿ Network test_default                  Created                                                                                1.6s
 ⠿ Volume "test_root_node_modules"       Created                                                                                0.0s
 ⠿ Volume "test_functions_node_modules"  Created                                                                                0.0s
 ⠿ Container test-postgres-1             Healthy                                                                                115.7s
 ⠿ Container test-functions-1            Healthy                                                                                104.3s
 ⠿ Container test-dashboard-1            Started                                                                                62.8s
 ⠿ Container test-minio-1                Started                                                                                53.5s
 ⠿ Container test-traefik-1              Started                                                                                85.0s
 ⠿ Container test-mailhog-1              Started                                                                                45.9s
 ⠿ Container test-graphql-1              Error                                                                                113.7s
 ⠿ Container test-storage-1              Created                                                                                11.8s
 ⠿ Container test-auth-1                 Created                                                                                10.0s
 ⠿ Container test-console-1              Created                                                                                10.9s
dependency failed to start: container test-graphql-1 is unhealthy
failed to start Nhost development environment: failed to start docker compose: exit status 1
- Do you want to stop Nhost's development environment? [y/N] n

andre in Documents/scratch/test at ubuntu-vm at ☸  do-sfo3-lambdo-posthog-k8s took 2m 24s
➜ nhost up
Setting up Nhost development environment...
Starting Nhost development environment...
[+] Running 10/10
 ⠿ Container test-postgres-1   Healthy                                                                                30.5s
 ⠿ Container test-minio-1      Healthy                                                                                29.1s
 ⠿ Container test-functions-1  Healthy                                                                                29.1s
 ⠿ Container test-dashboard-1  Healthy                                                                                29.1s
 ⠿ Container test-traefik-1    Healthy                                                                                29.1s
 ⠿ Container test-mailhog-1    Healthy                                                                                29.1s
 ⠿ Container test-graphql-1    Healthy                                                                                30.5s
 ⠿ Container test-storage-1    Healthy                                                                                28.1s
 ⠿ Container test-console-1    Healthy                                                                                28.1s
 ⠿ Container test-auth-1       Healthy                                                                                78.4s
Applying migrations...
INFO nothing to apply on database: default
Restarting services to reapply metadata if needed...
[+] Running 3/3
 ⠿ Container test-functions-1  Started                                                                                35.6s
 ⠿ Container test-auth-1       Started                                                                                35.4s
 ⠿ Container test-storage-1    Started                                                                                32.8s
Downloading metadata
INFO Help us improve Hasura! The cli collects anonymized usage stats which
allow us to keep improving Hasura at warp speed. To opt-out or read more,
visit https://hasura.io/docs/latest/graphql/core/guides/telemetry.html
Nhost development environment started.
URLs:
- Postgres:             postgres://postgres:postgres@localhost:5432/local
- Hasura:               https://local.hasura.nhost.run
- GraphQL:              https://local.graphql.nhost.run
- Auth:                 https://local.auth.nhost.run
- Storage:              https://local.storage.nhost.run
- Functions:            https://local.functions.nhost.run
- Dashboard:            https://local.dashboard.nhost.run
- Mailhog:              https://local.mailhog.nhost.run

SDK Configuration:
 Subdomain:             local
 Region:                (empty)

Run `nhost up` to reload the development environment
Run `nhost down` to stop the development environment
Run `nhost logs` to watch the logs

andre in Documents/scratch/test at ubuntu-vm at ☸  do-sfo3-lambdo-posthog-k8s took 3m 4s
➜

Here's the relevant logs
test-graphql-1    | {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T06:03:54.975+0000","type":"pg-client"}
test-graphql-1    | {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T06:03:54.975+0000","type":"pg-client"}
test-graphql-1    | {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T06:03:54.975+0000","type":"startup"}
test-graphql-1    | {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"}
test-graphql-1    | {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T06:04:19.063+0000","type":"pg-client"}
test-graphql-1    | {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T06:04:19.063+0000","type":"pg-client"}
test-graphql-1    | {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T06:04:19.063+0000","type":"startup"}
test-graphql-1    | {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"}
test-graphql-1    | {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T06:04:45.323+0000","type":"pg-client"}

One thought is maybe HASURA_GRAPHQL_PG_TIMEOUT or HASURA_GRAPHQL_NO_OF_RETRIES needs to be increased but I'm not sure if it's possible to set those that in the nhost.toml is it?
nhost version v1.5.2
Docker Compose version v2.20.2
Docker version 24.0.5, build v24.0.5
Tested on ubuntu and nixos

These are the logs for postgres
nhost logs postgres -t
test-postgres-1  | 2023-08-03T06:25:20.138381074Z Resolving pg_hba.conf
test-postgres-1  | 2023-08-03T06:25:20.141027713Z Waiting for postgres to start
test-postgres-1  | 2023-08-03T06:25:20.166788549Z The files belonging to this database system will be owned by user "postgres".
test-postgres-1  | 2023-08-03T06:25:20.166803149Z This user must also own the server process.
test-postgres-1  | 2023-08-03T06:25:20.166805259Z
test-postgres-1  | 2023-08-03T06:25:20.166819959Z The database cluster will be initialized with locale "en_US.UTF-8".
test-postgres-1  | 2023-08-03T06:25:20.166829890Z The default database encoding has accordingly been set to "UTF8".
test-postgres-1  | 2023-08-03T06:25:20.166832750Z The default text search configuration will be set to "english".
test-postgres-1  | 2023-08-03T06:25:20.166834890Z
test-postgres-1  | 2023-08-03T06:25:20.166837170Z Data page checksums are disabled.
test-postgres-1  | 2023-08-03T06:25:20.166843980Z
test-postgres-1  | 2023-08-03T06:25:20.166857310Z fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
test-postgres-1  | 2023-08-03T06:25:20.167140826Z creating subdirectories ... ok
test-postgres-1  | 2023-08-03T06:25:20.167191977Z selecting dynamic shared memory implementation ... posix
test-postgres-1  | 2023-08-03T06:25:20.174890387Z selecting default max_connections ... 100
test-postgres-1  | 2023-08-03T06:25:20.185618033Z selecting default shared_buffers ... 128MB
test-postgres-1  | 2023-08-03T06:25:20.192701198Z selecting default time zone ... Etc/UTC
test-postgres-1  | 2023-08-03T06:25:20.193763172Z creating configuration files ... ok
test-postgres-1  | 2023-08-03T06:25:20.344442284Z running bootstrap script ... ok
test-postgres-1  | 2023-08-03T06:25:20.650208604Z performing post-bootstrap initialization ... ok
test-postgres-1  | 2023-08-03T06:25:44.177642325Z syncing data to disk ... ok
test-postgres-1  | 2023-08-03T06:25:44.177659386Z
test-postgres-1  | 2023-08-03T06:25:44.177661936Z
test-postgres-1  | 2023-08-03T06:25:44.177663626Z Success. You can now start the database server using:
test-postgres-1  | 2023-08-03T06:25:44.177665386Z
test-postgres-1  | 2023-08-03T06:25:44.177666876Z     pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start
test-postgres-1  | 2023-08-03T06:25:44.177668536Z
test-postgres-1  | 2023-08-03T06:25:44.177694987Z initdb: warning: enabling "trust" authentication for local connections
test-postgres-1  | 2023-08-03T06:25:44.177704067Z You can change this by editing pg_hba.conf or using the option -A, or
test-postgres-1  | 2023-08-03T06:25:44.177706937Z --auth-local and --auth-host, the next time you run initdb.
test-postgres-1  | 2023-08-03T06:25:44.231859907Z waiting for server to start....2023-08-03 06:25:44.231 UTC () [472] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
test-postgres-1  | 2023-08-03T06:25:44.245160360Z 2023-08-03 06:25:44.245 UTC () [472] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
test-postgres-1  | 2023-08-03T06:25:44.315674579Z 2023-08-03 06:25:44.315 UTC () [476] LOG:  database system was shut down at 2023-08-03 06:25:20 UTC
test-postgres-1  | 2023-08-03T06:25:44.848507860Z 2023-08-03 06:25:44.848 UTC () [472] LOG:  database system is ready to accept connections
test-postgres-1  | 2023-08-03T06:25:44.892081778Z  done
test-postgres-1  | 2023-08-03T06:25:44.892107458Z server started
test-postgres-1  | 2023-08-03T06:26:05.762613698Z CREATE DATABASE
test-postgres-1  | 2023-08-03T06:26:05.763057418Z
test-postgres-1  | 2023-08-03T06:26:05.763135320Z
test-postgres-1  | 2023-08-03T06:26:05.763168471Z /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/0001-create-schema.sql
test-postgres-1  | 2023-08-03T06:26:06.235522903Z CREATE ROLE
test-postgres-1  | 2023-08-03T06:26:06.695925292Z ALTER ROLE
test-postgres-1  | 2023-08-03T06:26:07.155354910Z CREATE ROLE
test-postgres-1  | 2023-08-03T06:26:07.627246421Z GRANT ROLE
test-postgres-1  | 2023-08-03T06:26:08.063996239Z GRANT
test-postgres-1  | 2023-08-03T06:26:08.529866939Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T06:26:09.276204123Z ALTER SCHEMA
test-postgres-1  | 2023-08-03T06:26:10.326985618Z GRANT
test-postgres-1  | 2023-08-03T06:26:11.044906778Z GRANT
test-postgres-1  | 2023-08-03T06:26:11.523681813Z GRANT
test-postgres-1  | 2023-08-03T06:26:11.524068191Z GRANT
test-postgres-1  | 2023-08-03T06:26:11.524185783Z GRANT
test-postgres-1  | 2023-08-03T06:26:11.525104463Z GRANT
test-postgres-1  | 2023-08-03T06:26:12.010221615Z CREATE ROLE
test-postgres-1  | 2023-08-03T06:26:12.504496219Z ALTER ROLE
test-postgres-1  | 2023-08-03T06:26:12.992925054Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T06:26:13.480104052Z GRANT
test-postgres-1  | 2023-08-03T06:26:13.948447446Z CREATE ROLE
test-postgres-1  | 2023-08-03T06:26:14.373357345Z ALTER ROLE
test-postgres-1  | 2023-08-03T06:26:14.919348235Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T06:26:14.952607797Z GRANT
test-postgres-1  | 2023-08-03T06:26:14.963346863Z ALTER DEFAULT PRIVILEGES
test-postgres-1  | 2023-08-03T06:26:14.973157889Z ALTER DEFAULT PRIVILEGES
test-postgres-1  | 2023-08-03T06:26:14.989447176Z GRANT
test-postgres-1  | 2023-08-03T06:26:14.997427671Z GRANT
test-postgres-1  | 2023-08-03T06:26:15.010980020Z CREATE EXTENSION
test-postgres-1  | 2023-08-03T06:26:15.027962503Z CREATE EXTENSION
test-postgres-1  | 2023-08-03T06:26:15.034324423Z CREATE ROLE
test-postgres-1  | 2023-08-03T06:26:15.040408326Z REVOKE
test-postgres-1  | 2023-08-03T06:26:15.056202023Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T06:26:15.073219437Z CREATE FUNCTION
test-postgres-1  | 2023-08-03T06:26:15.083918683Z REVOKE
test-postgres-1  | 2023-08-03T06:26:15.157626982Z GRANT
test-postgres-1  | 2023-08-03T06:26:15.357752092Z GRANT
test-postgres-1  | 2023-08-03T06:26:15.358310643Z
test-postgres-1  | 2023-08-03T06:26:15.358321274Z
test-postgres-1  | 2023-08-03T06:26:15.358342744Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/0001-create-schema.sql.tmpl
test-postgres-1  | 2023-08-03T06:26:15.358356644Z
test-postgres-1  | 2023-08-03T06:26:15.358361345Z /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/XXXX-nhost.sql
test-postgres-1  | 2023-08-03T06:26:15.381221017Z GRANT ROLE
test-postgres-1  | 2023-08-03T06:26:15.381234627Z psql:/docker-entrypoint-initdb.d/XXXX-nhost.sql:1: NOTICE:  role "nhost_hasura" is already a member of role "postgres"
test-postgres-1  | 2023-08-03T06:26:15.381550325Z
test-postgres-1  | 2023-08-03T06:26:15.381559785Z
test-postgres-1  | 2023-08-03T06:26:15.381568775Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/XXXX-nhost.sql.tmpl
test-postgres-1  | 2023-08-03T06:26:15.381576595Z
test-postgres-1  | 2023-08-03T06:26:15.382197099Z 2023-08-03 06:26:15.382 UTC () [472] LOG:  received fast shutdown request
test-postgres-1  | 2023-08-03T06:26:16.329248103Z waiting for server to shut down....2023-08-03 06:26:16.329 UTC () [472] LOG:  aborting any active transactions
test-postgres-1  | 2023-08-03T06:26:16.330281405Z 2023-08-03 06:26:16.330 UTC () [472] LOG:  background worker "logical replication launcher" (PID 490) exited with exit code 1
test-postgres-1  | 2023-08-03T06:26:16.330456020Z 2023-08-03 06:26:16.330 UTC () [485] LOG:  shutting down
test-postgres-1  | 2023-08-03T06:26:20.020048270Z ....2023-08-03 06:26:20.019 UTC ([local]) [1128] FATAL:  the database system is shutting down
test-postgres-1  | 2023-08-03T06:26:24.729386835Z .....2023-08-03 06:26:24.729 UTC () [472] LOG:  database system is shut down
test-postgres-1  | 2023-08-03T06:26:24.799900865Z  done
test-postgres-1  | 2023-08-03T06:26:24.799911645Z server stopped
test-postgres-1  | 2023-08-03T06:26:24.800569599Z
test-postgres-1  | 2023-08-03T06:26:24.800577559Z PostgreSQL init process complete; ready for start up.
test-postgres-1  | 2023-08-03T06:26:24.800580549Z
test-postgres-1  | 2023-08-03T06:26:26.049957460Z 2023-08-03 06:26:26.049 UTC () [11] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
test-postgres-1  | 2023-08-03T06:26:26.049976510Z 2023-08-03 06:26:26.049 UTC () [11] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
test-postgres-1  | 2023-08-03T06:26:26.049979401Z 2023-08-03 06:26:26.049 UTC () [11] LOG:  listening on IPv6 address "::", port 5432
test-postgres-1  | 2023-08-03T06:26:27.214660489Z 2023-08-03 06:26:27.214 UTC () [11] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
test-postgres-1  | 2023-08-03T06:26:29.226708250Z 2023-08-03 06:26:29.226 UTC () [1239] LOG:  database system was shut down at 2023-08-03 06:26:24 UTC
test-postgres-1  | 2023-08-03T06:26:29.227985078Z 2023-08-03 06:26:29.227 UTC (test-graphql-1.test_default(36450)) [1241] FATAL:  the database system is starting up
test-postgres-1  | 2023-08-03T06:26:29.256029735Z 2023-08-03 06:26:29.255 UTC (localhost(44052)) [1243] FATAL:  the database system is starting up
test-postgres-1  | 2023-08-03T06:26:29.330190105Z 2023-08-03 06:26:29.330 UTC (test-graphql-1.test_default(36454)) [1245] FATAL:  the database system is starting up
test-postgres-1  | 2023-08-03T06:26:29.376158116Z 2023-08-03 06:26:29.376 UTC (localhost(44056)) [1247] FATAL:  the database system is starting up
test-postgres-1  | 2023-08-03T06:26:29.497468371Z 2023-08-03 06:26:29.497 UTC (localhost(44058)) [1250] FATAL:  the database system is starting up
test-postgres-1  | 2023-08-03T06:26:29.618454190Z 2023-08-03 06:26:29.618 UTC (localhost(44060)) [1253] FATAL:  the database system is starting up
test-postgres-1  | 2023-08-03T06:26:29.695814369Z 2023-08-03 06:26:29.695 UTC () [11] LOG:  database system is ready to accept connections
test-postgres-1  | 2023-08-03T06:26:30.781197785Z Running nhost.sql
test-postgres-1  | 2023-08-03T06:26:30.802708957Z GRANT ROLE
test-postgres-1  | 2023-08-03T06:26:30.802725587Z psql:/docker-entrypoint-initdb.d/XXXX-nhost.sql:1: NOTICE:  role "nhost_hasura" is already a member of role "postgres"
test-postgres-1  | 2023-08-03T16:53:17.905812320Z 2023-08-03 16:53:17.905 UTC ([local]) [47033] FATAL:  could not open file "global/pg_filenode.map": No such file or directory
test-postgres-1  | 2023-08-03T16:53:24.708107891Z 2023-08-03 16:53:24.708 UTC ([local]) [47041] FATAL:  could not open file "global/pg_filenode.map": No such file or directory
test-postgres-1  | 2023-08-03T16:53:30.401072630Z 2023-08-03 16:53:30.400 UTC ([local]) [47049] FATAL:  could not open file "global/pg_filenode.map": No such file or directory
test-postgres-1  | 2023-08-03T16:53:37.733220824Z 2023-08-03 16:53:37.733 UTC ([local]) [47057] FATAL:  could not open file "global/pg_filenode.map": No such file or directory
test-postgres-1  | 2023-08-03T16:53:42.836465808Z 2023-08-03 16:53:42.836 UTC ([local]) [47065] FATAL:  could not open file "global/pg_filenode.map": No such file or directory
test-postgres-1  | 2023-08-03T16:53:45.186532298Z 2023-08-03 16:53:45.186 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:45.607975386Z 2023-08-03 16:53:45.607 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:45.608000386Z 2023-08-03 16:53:45.607 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:45.830922526Z 2023-08-03 16:53:45.830 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:45.830948526Z 2023-08-03 16:53:45.830 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:46.475541718Z 2023-08-03 16:53:46.475 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:46.475565879Z 2023-08-03 16:53:46.475 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:46.609813325Z 2023-08-03 16:53:46.609 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:46.609830356Z 2023-08-03 16:53:46.609 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:47.120161820Z 2023-08-03 16:53:47.119 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:47.120187061Z 2023-08-03 16:53:47.120 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:47.466314406Z 2023-08-03 16:53:47.466 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:47.466329736Z 2023-08-03 16:53:47.466 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:47.764787783Z 2023-08-03 16:53:47.764 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:47.764808003Z 2023-08-03 16:53:47.764 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:48.409046097Z 2023-08-03 16:53:48.408 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:48.409066788Z 2023-08-03 16:53:48.408 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:48.613336801Z 2023-08-03 16:53:48.613 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:48.613362971Z 2023-08-03 16:53:48.613 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:49.054078738Z 2023-08-03 16:53:49.053 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:49.054096369Z 2023-08-03 16:53:49.054 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:49.615728712Z 2023-08-03 16:53:49.615 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:49.615749243Z 2023-08-03 16:53:49.615 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:49.698724441Z 2023-08-03 16:53:49.698 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:49.698739772Z 2023-08-03 16:53:49.698 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.343423125Z 2023-08-03 16:53:50.343 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.343444196Z 2023-08-03 16:53:50.343 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.618038191Z 2023-08-03 16:53:50.617 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.618055082Z 2023-08-03 16:53:50.617 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.953135536Z 2023-08-03 16:53:50.953 UTC () [11] LOG:  could not open file "postmaster.pid": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.953153247Z 2023-08-03 16:53:50.953 UTC () [11] LOG:  performing immediate shutdown because data directory lock file is invalid
test-postgres-1  | 2023-08-03T16:53:50.953155977Z 2023-08-03 16:53:50.953 UTC () [11] LOG:  received immediate shutdown request
test-postgres-1  | 2023-08-03T16:53:50.953158057Z 2023-08-03 16:53:50.953 UTC () [11] LOG:  could not open file "postmaster.pid": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.953241719Z 2023-08-03 16:53:50.953 UTC () [1259] LOG:  could not open temporary statistics file "pg_stat/global.tmp": No such file or directory
test-postgres-1  | 2023-08-03T16:53:50.957225486Z 2023-08-03 16:53:50.957 UTC () [11] LOG:  database system is shut down
test-postgres-1  | 2023-08-03T16:56:26.056579106Z Resolving pg_hba.conf
test-postgres-1  | 2023-08-03T16:56:26.472275810Z Waiting for postgres to start
test-postgres-1  | 2023-08-03T16:56:26.497470660Z The files belonging to this database system will be owned by user "postgres".
test-postgres-1  | 2023-08-03T16:56:26.497484170Z This user must also own the server process.
test-postgres-1  | 2023-08-03T16:56:26.497486730Z
test-postgres-1  | 2023-08-03T16:56:26.497488490Z The database cluster will be initialized with locale "en_US.UTF-8".
test-postgres-1  | 2023-08-03T16:56:26.497490480Z The default database encoding has accordingly been set to "UTF8".
test-postgres-1  | 2023-08-03T16:56:26.497492280Z The default text search configuration will be set to "english".
test-postgres-1  | 2023-08-03T16:56:26.497494120Z
test-postgres-1  | 2023-08-03T16:56:26.497495690Z Data page checksums are disabled.
test-postgres-1  | 2023-08-03T16:56:26.497497290Z
test-postgres-1  | 2023-08-03T16:56:26.497498781Z fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
test-postgres-1  | 2023-08-03T16:56:26.497730905Z creating subdirectories ... ok
test-postgres-1  | 2023-08-03T16:56:26.497780566Z selecting dynamic shared memory implementation ... posix
test-postgres-1  | 2023-08-03T16:56:26.504786749Z selecting default max_connections ... 100
test-postgres-1  | 2023-08-03T16:56:26.514783407Z selecting default shared_buffers ... 128MB
test-postgres-1  | 2023-08-03T16:56:26.521913373Z selecting default time zone ... Etc/UTC
test-postgres-1  | 2023-08-03T16:56:26.522965496Z creating configuration files ... ok
test-postgres-1  | 2023-08-03T16:56:26.595045947Z running bootstrap script ... ok
test-postgres-1  | 2023-08-03T16:56:26.866948866Z performing post-bootstrap initialization ... ok
test-postgres-1  | 2023-08-03T16:56:35.713892605Z syncing data to disk ... ok
test-postgres-1  | 2023-08-03T16:56:35.713914405Z
test-postgres-1  | 2023-08-03T16:56:35.713922575Z
test-postgres-1  | 2023-08-03T16:56:35.713924295Z Success. You can now start the database server using:
test-postgres-1  | 2023-08-03T16:56:35.713925915Z
test-postgres-1  | 2023-08-03T16:56:35.713927446Z     pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start
test-postgres-1  | 2023-08-03T16:56:35.713929046Z
test-postgres-1  | 2023-08-03T16:56:35.713903085Z initdb: warning: enabling "trust" authentication for local connections
test-postgres-1  | 2023-08-03T16:56:35.713943616Z You can change this by editing pg_hba.conf or using the option -A, or
test-postgres-1  | 2023-08-03T16:56:35.713948556Z --auth-local and --auth-host, the next time you run initdb.
test-postgres-1  | 2023-08-03T16:56:37.957320601Z waiting for server to start......2023-08-03 16:56:37.957 UTC () [215] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
test-postgres-1  | 2023-08-03T16:56:38.728285662Z 2023-08-03 16:56:38.728 UTC () [215] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
test-postgres-1  | 2023-08-03T16:56:39.152178414Z .2023-08-03 16:56:39.151 UTC () [279] LOG:  database system was shut down at 2023-08-03 16:56:26 UTC
test-postgres-1  | 2023-08-03T16:56:39.176087195Z 2023-08-03 16:56:39.176 UTC () [215] LOG:  database system is ready to accept connections
test-postgres-1  | 2023-08-03T16:56:39.233121808Z  done
test-postgres-1  | 2023-08-03T16:56:39.233154399Z server started
test-postgres-1  | 2023-08-03T16:56:57.026910562Z CREATE DATABASE
test-postgres-1  | 2023-08-03T16:56:57.027444374Z
test-postgres-1  | 2023-08-03T16:56:57.027562296Z
test-postgres-1  | 2023-08-03T16:56:57.027601507Z /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/0001-create-schema.sql
test-postgres-1  | 2023-08-03T16:56:58.040723788Z CREATE ROLE
test-postgres-1  | 2023-08-03T16:56:59.077430363Z ALTER ROLE
test-postgres-1  | 2023-08-03T16:56:59.927264504Z CREATE ROLE
test-postgres-1  | 2023-08-03T16:57:00.797057899Z GRANT ROLE
test-postgres-1  | 2023-08-03T16:57:02.056938481Z GRANT
test-postgres-1  | 2023-08-03T16:57:02.954893621Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T16:57:03.640294226Z ALTER SCHEMA
test-postgres-1  | 2023-08-03T16:57:04.110763615Z GRANT
test-postgres-1  | 2023-08-03T16:57:04.572799909Z GRANT
test-postgres-1  | 2023-08-03T16:57:05.035076389Z GRANT
test-postgres-1  | 2023-08-03T16:57:05.035357765Z GRANT
test-postgres-1  | 2023-08-03T16:57:05.035420176Z GRANT
test-postgres-1  | 2023-08-03T16:57:05.036158633Z GRANT
test-postgres-1  | 2023-08-03T16:57:05.641384910Z CREATE ROLE
test-postgres-1  | 2023-08-03T16:57:06.180042965Z ALTER ROLE
test-postgres-1  | 2023-08-03T16:57:06.217630994Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T16:57:06.235271119Z GRANT
test-postgres-1  | 2023-08-03T16:57:06.258555106Z CREATE ROLE
test-postgres-1  | 2023-08-03T16:57:06.270107308Z ALTER ROLE
test-postgres-1  | 2023-08-03T16:57:06.310092821Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T16:57:06.320756303Z GRANT
test-postgres-1  | 2023-08-03T16:57:06.623629637Z ALTER DEFAULT PRIVILEGES
test-postgres-1  | 2023-08-03T16:57:07.044921874Z ALTER DEFAULT PRIVILEGES
test-postgres-1  | 2023-08-03T16:57:07.537893373Z GRANT
test-postgres-1  | 2023-08-03T16:57:08.425907306Z GRANT
test-postgres-1  | 2023-08-03T16:57:09.329243872Z CREATE EXTENSION
test-postgres-1  | 2023-08-03T16:57:11.211254440Z CREATE EXTENSION
test-postgres-1  | 2023-08-03T16:57:11.957573084Z CREATE ROLE
test-postgres-1  | 2023-08-03T16:57:12.913669762Z REVOKE
test-postgres-1  | 2023-08-03T16:57:13.834677755Z CREATE SCHEMA
test-postgres-1  | 2023-08-03T16:57:14.580905235Z CREATE FUNCTION
test-postgres-1  | 2023-08-03T16:57:15.529356577Z REVOKE
test-postgres-1  | 2023-08-03T16:57:16.248665012Z GRANT
test-postgres-1  | 2023-08-03T16:57:17.745436667Z GRANT
test-postgres-1  | 2023-08-03T16:57:17.746277875Z
test-postgres-1  | 2023-08-03T16:57:17.746310796Z
test-postgres-1  | 2023-08-03T16:57:17.746317906Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/0001-create-schema.sql.tmpl
test-postgres-1  | 2023-08-03T16:57:17.746323996Z
test-postgres-1  | 2023-08-03T16:57:17.746332076Z /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/XXXX-nhost.sql
test-postgres-1  | 2023-08-03T16:57:17.768921300Z psql:/docker-entrypoint-initdb.d/XXXX-nhost.sql:1: NOTICE:  role "nhost_hasura" is already a member of role "postgres"
test-postgres-1  | 2023-08-03T16:57:17.768947410Z GRANT ROLE
test-postgres-1  | 2023-08-03T16:57:17.769295178Z
test-postgres-1  | 2023-08-03T16:57:17.769314498Z
test-postgres-1  | 2023-08-03T16:57:17.769321768Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/XXXX-nhost.sql.tmpl
test-postgres-1  | 2023-08-03T16:57:17.769323968Z
test-postgres-1  | 2023-08-03T16:57:17.770065274Z 2023-08-03 16:57:17.770 UTC () [215] LOG:  received fast shutdown request
test-postgres-1  | 2023-08-03T16:57:20.373946354Z waiting for server to shut down......2023-08-03 16:57:20.373 UTC () [215] LOG:  aborting any active transactions
test-postgres-1  | 2023-08-03T16:57:20.374856475Z 2023-08-03 16:57:20.374 UTC ([local]) [1015] FATAL:  the database system is shutting down
test-postgres-1  | 2023-08-03T16:57:20.375287584Z 2023-08-03 16:57:20.375 UTC () [215] LOG:  background worker "logical replication launcher" (PID 285) exited with exit code 1
test-postgres-1  | 2023-08-03T16:57:20.375380856Z 2023-08-03 16:57:20.375 UTC () [280] LOG:  shutting down
test-postgres-1  | 2023-08-03T16:57:28.915172270Z .........2023-08-03 16:57:28.915 UTC ([local]) [1163] FATAL:  the database system is shutting down
test-postgres-1  | 2023-08-03T16:57:31.922282612Z ...2023-08-03 16:57:31.922 UTC () [215] LOG:  database system is shut down
test-postgres-1  | 2023-08-03T16:57:31.993989525Z  done
test-postgres-1  | 2023-08-03T16:57:31.994002146Z server stopped
test-postgres-1  | 2023-08-03T16:57:31.994703381Z
test-postgres-1  | 2023-08-03T16:57:31.994713752Z PostgreSQL init process complete; ready for start up.
test-postgres-1  | 2023-08-03T16:57:31.994716832Z
test-postgres-1  | 2023-08-03T16:57:33.236936847Z 2023-08-03 16:57:33.236 UTC () [11] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
test-postgres-1  | 2023-08-03T16:57:33.236956107Z 2023-08-03 16:57:33.236 UTC () [11] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
test-postgres-1  | 2023-08-03T16:57:33.236959198Z 2023-08-03 16:57:33.236 UTC () [11] LOG:  listening on IPv6 address "::", port 5432

and these are the logs for graphql:
test-graphql-1  | 2023-08-03T06:25:58.753041537Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T06:25:58.751+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T06:25:58.853969476Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T06:25:58.751+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T06:25:58.853995257Z {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T06:25:58.751+0000","type":"startup"}
test-graphql-1  | 2023-08-03T06:25:58.854029747Z {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"}
test-graphql-1  | 2023-08-03T06:26:15.169148356Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T06:26:15.167+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T06:26:15.269949051Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T06:26:15.167+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T06:26:15.269968602Z {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T06:26:15.167+0000","type":"startup"}
test-graphql-1  | 2023-08-03T06:26:15.270012023Z {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"}
test-graphql-1  | 2023-08-03T06:26:29.228522360Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T06:26:29.228+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T06:26:29.330279517Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T06:26:29.228+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T06:26:29.330290758Z {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: FATAL:  the database system is starting up\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T06:26:29.228+0000","type":"startup"}
test-graphql-1  | 2023-08-03T06:26:29.330294948Z {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: FATAL:  the database system is starting up\n","path":"$"}
test-graphql-1  | 2023-08-03T06:26:50.525244062Z {"detail":"The following environment variables are deprecated and moved to metadata: HASURA_GRAPHQL_PG_CONNECTIONS, HASURA_GRAPHQL_PG_TIMEOUT, HASURA_GRAPHQL_TX_ISOLATION, HASURA_GRAPHQL_USE_PREPARED_STATEMENTS","level":"warn","timestamp":"2023-08-03T06:26:50.492+0000","type":"unstructured"}
test-graphql-1  | 2023-08-03T16:53:51.619567575Z WARNING:  terminating connection due to immediate shutdown command
test-graphql-1  | 2023-08-03T16:53:51.619743978Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:51.619+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:52.621496636Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:51.619+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:52.621521896Z {"detail":{"info":{"error":{"info":{"code":"postgres-error","error":"connection error","internal":"no connection to the server\n","path":"$"},"type":"query_error"}},"thread_type":"listener"},"level":"error","timestamp":"2023-08-03T16:53:51.619+0000","type":"schema-sync"}
test-graphql-1  | 2023-08-03T16:53:52.621529626Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:51.619+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:52.621533516Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:51.619+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:52.621537396Z {"detail":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"level":"error","timestamp":"2023-08-03T16:53:51.619+0000","type":"scheduled-trigger"}
test-graphql-1  | 2023-08-03T16:53:53.622918946Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:52.722+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:53.622954477Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:52.722+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:54.624185834Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:53.824+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:54.624212534Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:53.824+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:54.624217904Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:53.824+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:54.624221824Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:53.824+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:54.624228335Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"a657eb2d-0577-4fff-bdd3-0b4ac5f45f06","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"a657eb2d-0577-4fff-bdd3-0b4ac5f45f06"},"level":"error","timestamp":"2023-08-03T16:53:53.824+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:53:55.625401731Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:54.927+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:55.625437042Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:54.927+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:56.626165237Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:56.029+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:56.626190418Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:56.029+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:57.627600748Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:57.131+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:57.627626329Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:57.131+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:58.628665842Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:58.233+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:58.628694842Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:58.233+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:59.629108141Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:59.336+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:53:59.629134911Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:59.336+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:00.629514399Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:00.438+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:00.629536119Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:00.438+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:00.629541259Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:53:59.336+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:00.629544760Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:53:59.336+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:00.629550590Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"148321f6-6438-4cfa-b5a4-0d78bb614690","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"148321f6-6438-4cfa-b5a4-0d78bb614690"},"level":"error","timestamp":"2023-08-03T16:53:59.336+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:01.629918559Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:01.541+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:02.630164804Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:01.541+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:02.630188125Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:01.541+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:02.630192035Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:01.541+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:02.630198145Z {"detail":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"level":"error","timestamp":"2023-08-03T16:54:01.541+0000","type":"scheduled-trigger"}
test-graphql-1  | 2023-08-03T16:54:03.632033635Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:02.643+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:03.632063255Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:02.643+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:04.633517877Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:03.745+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:04.633548347Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:03.745+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:05.634882256Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:04.848+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:05.634902627Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:04.848+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:06.636240896Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:05.950+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:06.636259456Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:05.950+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:06.636263366Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:05.950+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:06.636266216Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:05.950+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:06.636271006Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"25be377a-84aa-4c76-a4aa-752fd8c8524f","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"25be377a-84aa-4c76-a4aa-752fd8c8524f"},"level":"error","timestamp":"2023-08-03T16:54:05.950+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:07.637670277Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:07.053+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:07.637698467Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:07.053+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:08.638871672Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:08.155+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:08.638901022Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:08.155+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:09.640061888Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:09.258+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:09.640091118Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:09.258+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:10.641383627Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:10.360+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:10.641412558Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:10.360+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:11.641743346Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:11.463+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:11.641770946Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:11.463+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:12.642232465Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:12.565+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:12.642276416Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:11.463+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:12.642281866Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:11.463+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:12.642286076Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:11.463+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:12.642289926Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"8cd3ae21-82d1-404e-a49a-bba902f2212c","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"8cd3ae21-82d1-404e-a49a-bba902f2212c"},"level":"error","timestamp":"2023-08-03T16:54:11.463+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:12.642311217Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:11.463+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:12.642318427Z {"detail":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"level":"error","timestamp":"2023-08-03T16:54:11.463+0000","type":"scheduled-trigger"}
test-graphql-1  | 2023-08-03T16:54:13.642519119Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:12.565+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:14.643673536Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:13.668+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:14.643702207Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:13.668+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:15.645040784Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:14.770+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:15.645064125Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:14.770+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:16.646074118Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:15.872+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:16.646100219Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:15.872+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:17.647287916Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:16.974+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:17.647310236Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:16.974+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:18.648374469Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:18.077+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:18.648395790Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:18.077+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:19.649646287Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:19.179+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:19.649675018Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:19.179+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:19.649680318Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:18.077+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:19.649697358Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:18.077+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:19.649704599Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"6b6f474a-ce0d-46ba-869c-8d43d3605a47","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"6b6f474a-ce0d-46ba-869c-8d43d3605a47"},"level":"error","timestamp":"2023-08-03T16:54:18.077+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:20.650879835Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:20.281+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:20.650906116Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:20.281+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:21.652034899Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:21.384+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:21.652059970Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:21.384+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:22.652381497Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:22.486+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:22.652404928Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:22.486+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:22.652410418Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:21.384+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:22.652414058Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:21.384+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:22.652417608Z {"detail":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"level":"error","timestamp":"2023-08-03T16:54:21.384+0000","type":"scheduled-trigger"}
test-graphql-1  | 2023-08-03T16:54:23.652693344Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:23.588+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:24.653558924Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:23.588+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:24.653609255Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:23.588+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:24.653635645Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:23.588+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:24.653642025Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"14c0e552-15f1-429e-84fd-fc4651a4949c","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"14c0e552-15f1-429e-84fd-fc4651a4949c"},"level":"error","timestamp":"2023-08-03T16:54:23.588+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:25.654645377Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:24.691+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:25.654670168Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:24.691+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:26.656294815Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:25.793+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:26.656317295Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:25.793+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:27.657509622Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:26.896+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:27.657533583Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:26.896+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:28.658779861Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:27.998+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:28.658802901Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:27.998+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:29.659669240Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:29.100+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:29.659690141Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:29.100+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:30.660805693Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:30.202+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:30.660840924Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:30.202+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:31.661269734Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:31.305+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:31.661299285Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:31.305+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:31.661303405Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:31.305+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:32.662208757Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:31.305+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:32.662230427Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"adb4dd14-1b34-454c-a5e2-439f9cfc42f2","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"adb4dd14-1b34-454c-a5e2-439f9cfc42f2"},"level":"error","timestamp":"2023-08-03T16:54:31.305+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:32.662237767Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:32.407+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:32.662240837Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:32.407+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:32.662243528Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:31.305+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:32.662246008Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:31.305+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:32.662248588Z {"detail":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"level":"error","timestamp":"2023-08-03T16:54:31.305+0000","type":"scheduled-trigger"}
test-graphql-1  | 2023-08-03T16:54:33.663336333Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:33.509+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:33.663364624Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:33.509+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:34.663572508Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:34.612+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:35.664033898Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:34.612+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:36.664981379Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:35.714+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:36.665033540Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:35.714+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:37.666274106Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:36.816+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:37.666305657Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:36.816+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:37.666311127Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:36.816+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:38.667754051Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:36.816+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:38.667786272Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"d33f32ed-a7cc-42f1-a44f-cf341354d96b","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"d33f32ed-a7cc-42f1-a44f-cf341354d96b"},"level":"error","timestamp":"2023-08-03T16:54:36.816+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:38.667801843Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:37.919+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:38.667807413Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:37.919+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:39.669301325Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:39.022+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:39.669324106Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:39.022+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:40.670899110Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:40.124+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:40.670921980Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:40.124+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:41.672015135Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:41.227+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:41.672056376Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:41.227+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:42.672742482Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:42.290+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:42.672764642Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:42.290+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:42.672778833Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:42.290+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:42.672782483Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:42.290+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:42.672785753Z {"detail":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"level":"error","timestamp":"2023-08-03T16:54:42.290+0000","type":"scheduled-trigger"}
test-graphql-1  | 2023-08-03T16:54:43.673640633Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:43.430+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:43.673665143Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:43.430+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:44.674164216Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:44.533+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:44.674194967Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:44.533+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:45.674643868Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:45.636+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:46.675066987Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:45.636+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:47.675658711Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:46.730+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:47.675686732Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:46.730+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:47.675698232Z {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"<IP_ADDRESS>","method":"GET","status":500,"url":"/healthz"},"operation":{"error":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"query":{"type":null},"request_id":"3e586f37-b9eb-4c5c-8a9a-1a0f2ef4b70b","request_mode":"error","response_size":238,"uncompressed_response_size":238},"request_id":"3e586f37-b9eb-4c5c-8a9a-1a0f2ef4b70b"},"level":"error","timestamp":"2023-08-03T16:54:46.730+0000","type":"http-log"}
test-graphql-1  | 2023-08-03T16:54:47.675719323Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:46.730+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:47.675727033Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:46.730+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:48.677273427Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:47.840+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:48.677294267Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:47.840+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:49.678683038Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:54:48.943+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:54:49.678705599Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:54:48.943+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:56:50.121485763Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:56:50.120+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:56:50.222091286Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:56:50.120+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:56:50.222106046Z {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T16:56:50.120+0000","type":"startup"}
test-graphql-1  | 2023-08-03T16:56:50.222116307Z {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"}
test-graphql-1  | 2023-08-03T16:57:19.557224925Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:57:19.555+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:57:19.657928571Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:57:19.555+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:57:19.657944141Z {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T16:57:19.555+0000","type":"startup"}
test-graphql-1  | 2023-08-03T16:57:19.657994612Z {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: Connection refused\n\tIs the server running on that host and accepting TCP/IP connections?\n","path":"$"}
test-graphql-1  | 2023-08-03T16:57:36.983873894Z {"detail":{"message":"postgres connection failed, retrying(0)."},"level":"warn","timestamp":"2023-08-03T16:57:36.983+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:57:37.086596773Z {"detail":{"message":"postgres connection failed, retrying(1)."},"level":"warn","timestamp":"2023-08-03T16:57:36.983+0000","type":"pg-client"}
test-graphql-1  | 2023-08-03T16:57:37.086624514Z {"detail":{"info":{"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: FATAL:  the database system is starting up\n","path":"$"},"kind":"catalog_migrate"},"level":"error","timestamp":"2023-08-03T16:57:36.983+0000","type":"startup"}
test-graphql-1  | 2023-08-03T16:57:37.086673085Z {"code":"postgres-error","error":"connection error","internal":"connection to server at \"postgres\" (<IP_ADDRESS>), port 5432 failed: FATAL:  the database system is starting up\n","path":"$"}
test-graphql-1  | 2023-08-03T16:58:12.219348888Z {"detail":"The following environment variables are deprecated and moved to metadata: HASURA_GRAPHQL_PG_CONNECTIONS, HASURA_GRAPHQL_PG_TIMEOUT, HASURA_GRAPHQL_TX_ISOLATION, HASURA_GRAPHQL_USE_PREPARED_STATEMENTS","level":"warn","timestamp":"2023-08-03T16:58:12.184+0000","type":"unstructured"}

looking at docker ps it looks like graphql restarts a few times.
But the first time it always shows:
Container test-graphql-1    Error                                                                                66.8s
dependency failed to start: container test-graphql-1 is unhealthy
failed to start Nhost development environment: failed to start docker compose: exit status 1
- Do you want to stop Nhost's development environment? [y/N]

So that means that the migrations/metadata don't get applied unless I run it the second time.

looking at docker ps it looks like graphql restarts a few times.

It is restarted twice to refresh the metadata (this is needed in case you have a remote schema running in a function), so this is expected.
I don't understand your postgres logs, are these from various runs? I see this:
test-postgres-1  | 2023-08-03T16:57:17.769323968Z
test-postgres-1  | 2023-08-03T16:57:17.770065274Z 2023-08-03 16:57:17.770 UTC () [215] LOG:  received fast shutdown request
test-postgres-1  | 2023-08-03T16:57:20.373946354Z waiting for server to shut down......2023-08-03 16:57:20.373 UTC () [215] LOG:  aborting any active transactions
test-postgres-1  | 2023-08-03T16:57:20.374856475Z 2023-08-03 16:57:20.374 UTC ([local]) [1015] FATAL:  the database system is shutting down

which I don't think it's expected. And the whole thing doesn't make sense either, the compose file is configured to have graphql wait until postgres is up and running.

Related the restarts are by design. here's some discussion: https://github.com/docker-library/postgres/issues/146

Sorry, I was off last week. I think the first step is to reproduce this issue because we can't and we haven't heard of any other reports. Do you have anything specific that could be triggering this? Can you reproduce on a new project?

Yes always happens to me on a clean project. The only thing that I believe could be unique to my setup is that I'm running it within a VM. Not sure if that would have any affect.

Technically, almost everybody runs this in a VM as neither windows nor Mac supports docker natively. Is there anything specific in your VM that could be interfering, i.e., SELinux? In any case, this is how the logs look like in a clean project;
asd-postgres-1  | Resolving pg_hba.conf
asd-postgres-1  | Waiting for postgres to start
asd-postgres-1  | The files belonging to this database system will be owned by user "postgres".
asd-postgres-1  | This user must also own the server process.
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | The database cluster will be initialized with locale "en_US.UTF-8".
asd-postgres-1  | The default database encoding has accordingly been set to "UTF8".
asd-postgres-1  | The default text search configuration will be set to "english".
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | Data page checksums are disabled.
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
asd-postgres-1  | creating subdirectories ... ok
asd-postgres-1  | selecting dynamic shared memory implementation ... posix
asd-postgres-1  | selecting default max_connections ... 100
asd-postgres-1  | selecting default shared_buffers ... 128MB
asd-postgres-1  | selecting default time zone ... Etc/UTC
asd-postgres-1  | creating configuration files ... ok
asd-postgres-1  | running bootstrap script ... ok
asd-postgres-1  | performing post-bootstrap initialization ... ok
asd-postgres-1  | syncing data to disk ... ok
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | Success. You can now start the database server using:
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |     pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | initdb: warning: enabling "trust" authentication for local connections
asd-postgres-1  | You can change this by editing pg_hba.conf or using the option -A, or
asd-postgres-1  | --auth-local and --auth-host, the next time you run initdb.
asd-postgres-1  | waiting for server to start....2023-08-15 07:57:54.258 UTC () [98] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
asd-postgres-1  | 2023-08-15 07:57:54.259 UTC () [98] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
asd-postgres-1  | 2023-08-15 07:57:54.264 UTC () [99] LOG:  database system was shut down at 2023-08-15 07:57:53 UTC
asd-postgres-1  | 2023-08-15 07:57:54.268 UTC () [98] LOG:  database system is ready to accept connections
asd-postgres-1  |  done
asd-postgres-1  | server started
asd-postgres-1  | CREATE DATABASE
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/0001-create-schema.sql
asd-postgres-1  | CREATE ROLE
asd-postgres-1  | ALTER ROLE
asd-postgres-1  | CREATE ROLE
asd-postgres-1  | GRANT ROLE
asd-postgres-1  | GRANT
asd-postgres-1  | CREATE SCHEMA
asd-postgres-1  | ALTER SCHEMA
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  | CREATE ROLE
asd-postgres-1  | ALTER ROLE
asd-postgres-1  | CREATE SCHEMA
asd-postgres-1  | GRANT
asd-postgres-1  | CREATE ROLE
asd-postgres-1  | ALTER ROLE
asd-postgres-1  | CREATE SCHEMA
asd-postgres-1  | GRANT
asd-postgres-1  | ALTER DEFAULT PRIVILEGES
asd-postgres-1  | ALTER DEFAULT PRIVILEGES
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  | CREATE EXTENSION
asd-postgres-1  | CREATE EXTENSION
asd-postgres-1  | CREATE ROLE
asd-postgres-1  | REVOKE
asd-postgres-1  | CREATE SCHEMA
asd-postgres-1  | CREATE FUNCTION
asd-postgres-1  | REVOKE
asd-postgres-1  | GRANT
asd-postgres-1  | GRANT
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/0001-create-schema.sql.tmpl
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/XXXX-nhost.sql
asd-postgres-1  | psql:/docker-entrypoint-initdb.d/XXXX-nhost.sql:1: NOTICE:  role "nhost_hasura" is already a member of role "postgres"
asd-postgres-1  | GRANT ROLE
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/XXXX-nhost.sql.tmpl
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | 2023-08-15 07:57:54.689 UTC () [98] LOG:  received fast shutdown request
asd-postgres-1  | waiting for server to shut down....2023-08-15 07:57:54.690 UTC () [98] LOG:  aborting any active transactions
asd-postgres-1  | 2023-08-15 07:57:54.695 UTC () [98] LOG:  background worker "logical replication launcher" (PID 105) exited with exit code 1
asd-postgres-1  | 2023-08-15 07:57:54.695 UTC () [100] LOG:  shutting down
asd-postgres-1  | 2023-08-15 07:57:54.742 UTC () [98] LOG:  database system is shut down
asd-postgres-1  |  done
asd-postgres-1  | server stopped
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | PostgreSQL init process complete; ready for start up.
asd-postgres-1  |
asd-postgres-1  |
asd-postgres-1  | 2023-08-15 07:57:54.803 UTC () [11] LOG:  starting PostgreSQL 14.6 (Debian 14.6-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
asd-postgres-1  | 2023-08-15 07:57:54.803 UTC () [11] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
asd-postgres-1  | 2023-08-15 07:57:54.803 UTC () [11] LOG:  listening on IPv6 address "::", port 5432
asd-postgres-1  | 2023-08-15 07:57:54.805 UTC () [11] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
asd-postgres-1  | 2023-08-15 07:57:54.810 UTC () [125] LOG:  database system was shut down at 2023-08-15 07:57:54 UTC
asd-postgres-1  | 2023-08-15 07:57:54.815 UTC () [11] LOG:  database system is ready to accept connections

The most notable difference from your logs is the timestamps. In your logs the timestamps don't make any sense, specially if you say they are from a single run. In my lgs you can see postgres barely takes 10s to start and become healthy but in yours things seem to span hours  and there are lots of errors about missing files.

I just tried on the latest version v1.5.3 in a new project and in an existing project and seems to be working now. Not sure what caused it originally. But thanks for looking at this!

Glad to hear :)


Pinch to zoom gesture not working on Android when used inside ScrollView

Describe the bug
When the Crop component is used inside of a ScrollView, the image can't be zoomed with 2 fingers on Android, instead the ScrollView is moving. Just moving the image with 1 finger works fine.
On iOS, everything works as expected.
To Reproduce
Steps to reproduce the behavior:

Put the <Crop> inside a <ScrollView>
Try to zoom the image with 2 fingers on Android
The screen is scrolling

Expected behavior
Pinch to zoom should work on Android also when used inside a ScrollView.
Smartphone:

OS: Android (tested with 7 and 11)

Additional context
Might be related: https://github.com/software-mansion/react-native-gesture-handler/issues/1082

change
import { ScrollView } from 'react-native';
to
import { ScrollView } from 'react-native-gesture-handler';

I tried that already, it didn't work.

Try following scrollview props, if it still doesn't work please create a reproducible repo
//...
import { ScrollView } from 'react-native';

//...
<ScrollView
disableScrollViewPanResponder={true}
nestedScrollEnabled={true}
pinchGestureEnabled={false}
>
<Crop>
//...
</ScrollView>

Thanks, I also didn't have luck with that.
I'm currently trying to setup a reproduction repo, but with a fresh project I can't get any gestures working on Android, even without using a ScrollView on this screen I can't move the image now. It's working fine on iOS.
So this repo it's showing the bug yet, but something else is already broken.
I'm giving up for today, but maybe you have an idea?
https://github.com/christianrank/react-native-avatar-crop-bug-reproduction

The example already uses a scrollview and it works,
https://github.com/vemarav/react-native-avatar-crop/blob/d0910826126869e22d82aa2d8acc0762df1a1fe9/example/CropImage.tsx#L46
use<EMAIL_ADDRESS>WIP to support react-native-gesture-handler v2

Please check #14 for the solution.

@vemarav
Which branch is this support work being done on? Keen to see it!


[FLINK-5495] [mesos] Provide executor to ZooKeeperMesosWorkerStore

The ZooKeeperMesosWorkerStore instantiates a ZooKeeperStateHandleStore which requires an
Executor instance. This executor is now given to the ZooKeeperMesosWorkerStore.

+1 to merge, LGTM.

Thanks for your review @tzulitai. Merging this PR.


docs[vi]: update config webhook, handle table event.

Codecov Report

Merging #77 (272207e) into main (d9547b6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #77   +/-   ##
=========================================
  Coverage     95.00%   95.00%
  Complexity      446      446
=========================================
  Files            96       96
  Lines          1722     1722
=========================================
  Hits           1636     1636
  Misses           86       86

Flag
Coverage Δ

phpunit
95.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d9547b6...272207e. Read the comment docs.


The latest LPC11U35 firmware update failed

Compile the latest source code, generate LPC11U35 firmware and found a direct U disk update firmware will fail, the previous firmware no problem, but the latest firmware can be used to burn the simulator can work, where changes lead to this problem?

Hi @neomissing, what do you mean by U disk update? What file are you loading? Is the device in CRP disabled mode?

lpc11u35_lpc824xpresso_if,the device in CRP disabled mode,update LPC11U35 firmware,

Try using lpc11u35_lpc824xpresso_if_crc.bin instead. CRP disabled mode requires the CRCed version of the binary.

Thanks,I try lpc11u35_lpc824xpresso_if_crc.bin ,it's OK.

Good to hear. Can this issue be closed?


fix: issue #627

When "create" rule involves foreign keys, don't generate input check guard.

Fixes #627


fix: pass correct delimiter

Consumers projects can have a package.json configuration which will use path-to-regexp 6.x or 5.x. Those versions have a different delimiter, which will cause bugs. We pass the delimiter that is used by default in older version of path-to-regexp
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?
Consumers projects can have a package.json configuration which will use
path-to-regexp 6.x or 5.x. Those versions have a different
delimiter, which will cause bugs. We pass the delimiter that is used
by default in older version of path-to-regexp
Issue Number: 1177
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[X ] No

Other information

fixes #1177


spot color layer completely black using tiffsep

Hi @NickNaso
thank you for this awesome work, it is really useful, but i had a problem that i guess is a bug.
When I try to use the tiffsep sDevice option some of the layers that are spot color are generated completely black.
I don't know the cause but if I try to run the same command in the shell it works.
// Run ghostscript
try {
	gs.executeSync('-dBATCH -dNOPAUSE -dSAFER -sDEVICE=tiffsep -dFirstPage=1 -dLastPage=1 -r144 -sOutputFile=output.tif "./input.pdf"')
} catch (err) {
	// Handle error
	console.error('gs =>', err)
}

Hi @daton89,
you need to remove the quotation marks from the path of the pdf file and use one of the command reported in the example below:
'use strict'

const gs = require('ghostscript4js')

try {
    // Command as a string
    gs.executeSync('-dBATCH -dNOPAUSE -dSAFER -sDEVICE=tiffsep -dFirstPage=1 -dLastPage=1 -r144 -sOutputFile=output.tif ./input.pdf')
    // Command as array of parameters
    gs.executeSync(['-dBATCH', '-dNOPAUSE', '-dSAFER', '-sDEVICE=tiffsep' ,'-dFirstPage=1', '-dLastPage=1', '-r144', '-sOutputFile=output.tif', './input.pdf'])
} catch (err) {
    // Handle error
    throw err
}

I think that this should solve your problem. Keep me updated about this.

Hi @NickNaso,
unfortunately it doesn't work.
Thanks