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
Bumps github.com/OpenAudio/go-openaudio and .../pkg/etl from 5d2e19a (#901) to 43606e8 to consume go-openaudio #337.
That change adds ETL migration 0031, which indexes track_routes and playlist_routes on (owner_id, title_slug, collision_id). Slug-collision resolution runs SELECT MAX(collision_id) … WHERE owner_id AND title_slug on every track/playlist create + rename; today that's a full per-owner route scan (prod EXPLAIN: ~16k-row bitmap heap scan on every upload for a prolific owner), which is the multi-second Track (7.8s) / Playlist (44s) tail in core-indexer. The new index makes it an index-only lookup.
core-indexer runs this vendored audius/api image, so this bump is required to ship #337 to prod.
Changes
go.mod / go.sum: both go-openaudio modules → v1.3.1-0.20260604005215-43606e8d8e5a
⚠️ Deploy note — pre-build the indexes CONCURRENTLY first
Migration 0031 builds the indexes non-concurrently (single-transaction migration runner), taking an ACCESS EXCLUSIVE lock on track_routes (~2M rows / 493 MB) on indexer boot. To avoid stalling route writes on deploy, pre-build them in prod first — IF NOT EXISTS then makes the migration a no-op (same pattern used to recover the 0030 indexes):
CREATEINDEXCONCURRENTLY IF NOT EXISTS track_routes_owner_title_slug_idx
ON track_routes (owner_id, title_slug, collision_id);
CREATEINDEXCONCURRENTLY IF NOT EXISTS playlist_routes_owner_title_slug_idx
ON playlist_routes (owner_id, title_slug, collision_id);
Test plan
go mod tidy — only go.mod/go.sum changed
go build ./... passes
migration 0031 present in the resolved module
Post-deploy: 0031 applied (or no-op if pre-built), and Track/Playlist max processing times drop in the indexer log analysis
Pulls go-openaudio 43606e8, which adds migration 0031 indexing
track_routes/playlist_routes on (owner_id, title_slug, collision_id).
This makes the per-upload slug-collision MAX(collision_id) lookup an
index-only scan instead of a full per-owner route scan, cutting the
multi-second Track/Playlist tail in core-indexer.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
… (#919)
## Summary
Bumps `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` from
`5d2e19a` (#901) to **`7062cd9`**. Because `7062cd9` is downstream of
both fixes, this single bump ships **two** changes to `core-indexer`:
> **Supersedes #912** (the standalone slug bump). #912 can be closed —
this bump includes everything in it plus #340.
## Changes
- `go.mod` / `go.sum`: both go-openaudio modules →
`v1.3.1-0.20260608175930-7062cd90dff5`
## ⚠️ Deploy note (carried from #337) — pre-build the indexes
CONCURRENTLY
This bump pulls migration `0031`, which builds two route indexes
**non-concurrently** (single-transaction migration runner), taking an
`ACCESS EXCLUSIVE` lock on `track_routes` (~2M rows / 493 MB) on indexer
boot. To avoid stalling route writes on deploy, pre-build them in prod
first — `IF NOT EXISTS` then makes the migration a no-op:
```sql
CREATE INDEX CONCURRENTLY IF NOT EXISTS track_routes_owner_title_slug_idx
ON track_routes (owner_id, title_slug, collision_id);
CREATE INDEX CONCURRENTLY IF NOT EXISTS playlist_routes_owner_title_slug_idx
ON playlist_routes (owner_id, title_slug, collision_id);
```
(The rune-count change in #340 is pure validation logic — no migration,
no special rollout.)
## Test plan
- [x] `go mod tidy` — only go.mod/go.sum changed
- [x] `go build ./...` passes
- [x] resolved module contains the rune-count fix (`RuneCountInString`
in validate.go) **and** migration `0031`
- [ ] Post-deploy: `g1ld3dd` (and other multi-byte-name users) can save
profile updates / artist picks; 0031 applied or no-op; Track/Playlist
max processing times drop
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
github.com/OpenAudio/go-openaudioand.../pkg/etlfrom5d2e19a(#901) to43606e8to consume go-openaudio #337.That change adds ETL migration
0031, which indexestrack_routesandplaylist_routeson(owner_id, title_slug, collision_id). Slug-collision resolution runsSELECT MAX(collision_id) … WHERE owner_id AND title_slugon every track/playlist create + rename; today that's a full per-owner route scan (prod EXPLAIN: ~16k-row bitmap heap scan on every upload for a prolific owner), which is the multi-second Track (7.8s) / Playlist (44s) tail incore-indexer. The new index makes it an index-only lookup.core-indexerruns this vendoredaudius/apiimage, so this bump is required to ship #337 to prod.Changes
go.mod/go.sum: both go-openaudio modules →v1.3.1-0.20260604005215-43606e8d8e5aMigration 0031 builds the indexes non-concurrently (single-transaction migration runner), taking an
ACCESS EXCLUSIVElock ontrack_routes(~2M rows / 493 MB) on indexer boot. To avoid stalling route writes on deploy, pre-build them in prod first —IF NOT EXISTSthen makes the migration a no-op (same pattern used to recover the 0030 indexes):Test plan
go mod tidy— only go.mod/go.sum changedgo build ./...passes0031present in the resolved module🤖 Generated with Claude Code