Skip to content

Fix repeated grabs of failed Usenet releases - #141

Open
Unthred wants to merge 1 commit into
Chaptarr:developfrom
Unthred:fix/issue-140-usenet-failed-release-dedupe
Open

Unthred wants to merge 1 commit into
Chaptarr:developfrom
Unthred:fix/issue-140-usenet-failed-release-dedupe

Conversation

@Unthred

@Unthred Unthred commented Sep 13, 2026

Copy link
Copy Markdown

Description

Reject a failed Usenet release when the same title is returned again for the same author, even if the indexer reports a different publication timestamp. This prevents automatic failed-download retries from repeatedly grabbing the same named release while preserving differently named replacement candidates.

Fixes #140

Database Migration

NO.

How was this tested?

  • Added a regression test covering a failed Usenet release whose publication timestamp changes between indexer responses.
  • Ran dotnet test src/Chaptarr.Core.Test/Chaptarr.Core.Test.csproj -p:TreatWarningsAsErrors=false -p:WarningsNotAsErrors=NU1902 in an isolated .NET 10 Docker SDK environment: 3,021 passed, 0 failed.
  • The repository currently emits the existing NU1902 advisory for Microsoft.Build.Tasks.Git 8.0.0; it was left as a warning so the existing suite could run.

Screenshots (UI changes only)

Not applicable.

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.

[BUG] Failed Usenet releases can be repeatedly re-grabbed when the indexer varies publish dates

1 participant