Refresh HiveGrid Cloud reference snapshot

This commit is contained in:
david committed 2026-08-03 15:31:14 +02:00
1 parent 5e99e14772
commit 7f88026f79
5955 files changed
+1177325 -188362

No files matched your search

@@ -77,7 +77,13 @@ docker run --rm -d \
"$PG_IMAGE" >/dev/null
deadline=$(( $(date +%s) + 30 ))
until docker exec "$DRILL_NAME" pg_isready -U "$DRILL_USER" -d "$DRILL_DB" >/dev/null 2>&1; do
# Probe over TCP, not the unix socket. On first boot the postgres image starts a
# temporary server that listens on the socket ONLY (initdb + init scripts), then
# shuts it down before starting the real one. A socket-based pg_isready reports
# ready during that window, so the very next psql can hit
# "FATAL: the database system is shutting down". The temp server sets
# listen_addresses='', so a TCP probe cannot succeed too early.
until docker exec "$DRILL_NAME" pg_isready -h 127.0.0.1 -U "$DRILL_USER" -d "$DRILL_DB" >/dev/null 2>&1; do
if [ "$(date +%s)" -gt "$deadline" ]; then
echo "FAIL postgres did not become ready within 30s" >&2
exit 1
@@ -90,7 +96,6 @@ echo "PHASE 1/4 applying forward migration chain"
DATABASE_URL="$DRILL_DATABASE_URL" pnpm --filter @hivegrid/db prisma:generate >/dev/null
DATABASE_URL="$DRILL_DATABASE_URL" pnpm exec prisma migrate deploy --schema prisma/schema/schema.prisma
forward_count=$(DATABASE_URL="$DRILL_DATABASE_URL" pnpm exec prisma migrate status --schema prisma/schema/schema.prisma 2>&1 | grep -c "Following migration have been applied" || true)
echo "PASS forward migration chain applied"
if [ "$RUN_SEED" = "1" ]; then