You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A migration was accidentally added that had a hard-coded reference to "public". We can't just remove that because it will cause a mismatch between the applied migrations table hash and the migration files.
Potential fix
Update the migration to fix it.
Add a script that runs before db migrate deploy in shell startup script.
Update hash for the bad migration.
Make that SQL available to run somewhere else, maybe in a Readme
A temporary workaround for new docker deploys: (do NOT use for existing deploys!)
services:
triggerdotdev:
# These values may differ in your deploy image: ghcr.io/triggerdotdev/trigger.dev:latestcontainer_name: triggerdotdevrestart: alwaysenv_file:
- .envports:
- 3030:3030depends_on:
- triggerdotdev-databasenetworks:
- app_network# This is the important bit!command:
- sh
- -c
- sed -i s/public/triggerdotdev/ ./packages/database/prisma/migrations/20240130165343_add_composite_index_to_job_run_for_job_id_and_created_at/migration.sql && ./scripts/entrypoint.sh
A migration was accidentally added that had a hard-coded reference to "public". We can't just remove that because it will cause a mismatch between the applied migrations table hash and the migration files.
Potential fix
db migrate deploy
in shell startup script.From SyncLinear.com | TRI-1948
The text was updated successfully, but these errors were encountered: