Skip to content

fix: always close comparison scrape pages (#162) - #178

Merged
atomantic merged 3 commits into
mainfrom
claim/issue-162
Aug 30, 2026
Merged

fix: always close comparison scrape pages (#162)#178
atomantic merged 3 commits into
mainfrom
claim/issue-162

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Summary

  • close every temporary comparison scrape page through an awaited finally, including failed Ancestry navigation and scraping
  • log page-close failures with provider and external-ID context without masking the primary failure
  • prevent failed refresh paths from reaching cache, photo, parent-link, or augmentation mutations, with focused regression coverage

Test plan

  • npm test -- --run tests/unit/services/multiPlatformComparison.spec.ts
  • npm test -- --run tests/unit
  • npm run build
  • npm run check:file-sizes

Closes #162

@atomantic
atomantic merged commit b9b6f44 into main Aug 30, 2026
4 checks passed
@atomantic
atomantic deleted the claim/issue-162 branch August 30, 2026 23:38
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.

Always close comparison scrape pages when setup fails

1 participant