[GH] (texera/fix/local-dev-fresh-db-replay): Workflow run "Required Checks" is working again!

[GitBox <gi...@apache.org>]

The GitHub Actions job "Required Checks" on texera.git/fix/local-dev-fresh-db-replay has succeeded.
Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).

Head commit for run:
19364e77fa14c0aab1d78f188c45704a67d7bc87 / Yicong Huang <17...@users.noreply.github.com>
fix(local-dev): don't abort `up` on an already-applied sql/updates changeSet

On a fresh docker volume postgres applies sql/texera_ddl.sql itself — compose
mounts sql/ into /docker-entrypoint-initdb.d — and that DDL is kept in sync
with sql/updates/*, so the changeSets local-dev replays immediately afterwards
re-create objects that are already there. 23-27 are incidentally idempotent
and pass; 28.sql's dataset_owner_uid_name_key is not, so `up` died before the
sbt build ever started. The `seed` path written for exactly this case was
unreachable, because the container entrypoint always wins the race.

Treat a psql failure whose every ERROR line is "already exists" as
already-applied: record the changeSet and carry on. The check is deliberately
narrow — a duplicate-key conflict is a data problem, and a failure with no
ERROR line at all is never assumed harmless — so an incomplete schema still
stops the build instead of reaching jOOQ codegen.

psql's stderr is also kept rather than sent to /dev/null, so a real failure
no longer requires re-running the file by hand to find out why.

Closes #7064

Report URL: https://github.com/apache/texera/actions/runs/30498196356

With regards,
GitHub Actions via GitBox