The GitHub Actions job "Backport Checks" on texera.git/fix/8721-example-loader-owner-email has succeeded. Run started by GitHub user mengw15 (triggered by mengw15).
Head commit for run: a457a58d7bbe95b8b9e40ecf897e69e267dcfdd7 / mengw15 <[email protected]> fix(deploy): load example datasets against the account's real email The example loader derived the owner email file-service looks datasets up by from the username, concatenating "@example.com" onto it. On a single-node deployment that never matches: the admin seeded from USER_SYS_ADMIN_USERNAME has the username itself as its email, so every example file upload failed with 400 "Dataset not found". Both example datasets were created but left with no files and no version, leaving the two example workflows pointing at CSV paths that do not exist. Take the email from the access token's "email" claim instead, so it is whatever the server actually stored -- correct both for the seeded admin and for an account this script had to register itself. The register call keeps an @-shaped address, which the server's format check requires. Also make the loader exit non-zero once it has logged an error. Each failure stays non-fatal so one bad file does not abandon the rest, but they used to leave no trace at all: the container printed "Example data loading complete" and exited 0, which is why this went unnoticed. Report URL: https://github.com/apache/texera/actions/runs/36358345663 With regards, GitHub Actions via GitBox
