Skip to content

fix: blank Scrapers page on databases with high scene counts#2135

Open
mvdeckard wants to merge 2 commits intoxbapps:masterfrom
mvdeckard:fix/scraper-fixes
Open

fix: blank Scrapers page on databases with high scene counts#2135
mvdeckard wants to merge 2 commits intoxbapps:masterfrom
mvdeckard:fix/scraper-fixes

Conversation

@mvdeckard
Copy link
Contributor

@mvdeckard mvdeckard commented Jan 21, 2026

Summary

  • Fix blank Scrapers page issue affecting some users with larger scene databases (20k+ scenes) and on resource-constrained systems (NAS/Docker)
  • Replace N individual COUNT queries with single GROUP BY query
  • Use map-based lookup for HasScraper check instead of nested loop
  • Add index on scenes.scraper_id via migration

- Fix Scrapers page not showing scrapers on slow devices due to race
  condition with async store loading. Changed showAllScrapers to local
  component state with default true instead of persisted store state.

- Fix Auto-limit scraping being enabled even when scrape failed (e.g.,
  "Studio code not found" errors). Now only enables after successful scrape.

- Fix SLR URL generation producing invalid double-dash URLs. Now uses the
  `label` field from SLR API directly instead of regenerating URL slugs
  from titles, preserving legitimate double-dash URLs while avoiding
  invalid ones.

- Disable limit scraping when user selects "Force update scenes" to allow
  full re-scrape, matching the behavior of "Delete scraped scenes".
@mvdeckard mvdeckard changed the title hotfix: Scrapers page blank list on large databases fix: blank Scrapers page on databases with high scene counts Jan 21, 2026
- Replace N individual COUNT queries with single GROUP BY query
- Use map-based lookup for HasScraper check instead of nested loop
- Add index on scenes.scraper_id via migration for existing users
- Add gorm index annotation for new installs

Fixes blank Scrapers page issue affecting users with large scene databases
(20k+ scenes) on resource-constrained systems (NAS/Docker).
@toshski
Copy link
Contributor

toshski commented Feb 3, 2026

FYI: It probably doesn't matter for adding an index, but migrations that change the schema should go further up the migration list.

Search for the line (currently about 850)
// Put DB Schema migrations above this line and migrations that rely on the updated schema below

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants