Devin AI
3e491df445
Phase 0 of the LLM model registry productionization pipeline:
- non-blocking sync-prices:check job wired into pr_checks.yml
- OTEL counter llm_missing_model_enrichment{gen_ai_system, has_provider_cost}
emitted from enrichCreatableEvents when the registry is loaded but a span
can't be priced
Phase 1 schema + registry wiring (additive, no breaking changes):
- New LlmModel columns: resolvedAt, needsReview, releaseDate, deprecationDate,
knowledgeCutoff, supportsStructuredOutput, supportsParallelToolCalls,
supportsStreamingToolCalls
- ModelPricingRegistry.loadFromDatabase filters needsReview=true rows so
auto-priced and freshly-synced rows stay out of the live registry until
admin approval
- New LlmRegistryPubSub service on channel llm-registry:reload so webapp
replicas pick up DB changes within seconds (5-min periodic reload kept as
backstop)
- llmPricingRegistry subscribes on boot; publishLlmRegistryReload() exposed
for admin routes + future cloud-repo trigger.dev tasks
- Admin API (create/update/delete/reload/seed) and admin UI routes now
publish on the channel after mutations and accept the widened source enum
(langfuse, auto, research, provider-api) + the new review/metadata fields
Co-Authored-By: Eric Allam <eallam@icloud.com>
@trigger.dev/database
This is the internal database package for the Trigger.dev project. It exports a generated prisma client that can be instantiated with a connection string.
How to switch branches when you've done migrations
Sometimes you've applied migrations and then want to switch branches without wiping out your local database.
To do this you can run the following command:
DB_VOLUME=database-data-alt pnpm run docker
This will switch to the alt volume for your local database. This database will be blank if you haven't switched to this volume before, so you'll need to follow the normal steps (in the Contributing guide) to get setup, e.g. apply migrations and seed.
To switch back to the original volume, run the following command:
pnpm run docker
How to add a new index on a large table
- Modify the Prisma.schema with a single index change (no other changes, just one index at a time)
- Create a Prisma migration using
cd internal-packages/database && pnpm run db:migrate:dev:create - Modify the SQL file: add IF NOT EXISTS to it and CONCURRENTLY:
CREATE INDEX CONCURRENTLY IF NOT EXISTS "JobRun_eventId_idx" ON "JobRun" ("eventId");
- Don’t apply the Prisma migration locally yet. This is a good opportunity to test the flow.
- Manually apply the index to your database, by running the index command.
- Then locally run
pnpm run db:migrate:deploy
Before deploying
Run the index creation before deploying
CREATE INDEX CONCURRENTLY IF NOT EXISTS "JobRun_eventId_idx" ON "JobRun" ("eventId");
These commands are useful:
-- creates an index safely, this can take a long time (2 mins maybe)
CREATE INDEX CONCURRENTLY IF NOT EXISTS "JobRun_eventId_idx" ON "JobRun" ("eventId");
-- checks the status of an index
SELECT * FROM pg_stat_progress_create_index WHERE relid = '"JobRun"'::regclass;
-- checks if the index is there
SELECT * FROM pg_indexes WHERE tablename = 'JobRun' AND indexname = 'JobRun_eventId_idx';
Now, when you deploy and prisma runs the migration, it will skip the index creation because it already exists. If you don't do this, there will be pain.