Skip to content

Don't report an empty aggregator set as a failed restore#101

Merged
d4rken merged 1 commit into
devfrom
fix/restore-empty-aggregators
Jun 19, 2026
Merged

Don't report an empty aggregator set as a failed restore#101
d4rken merged 1 commit into
devfrom
fix/restore-empty-aggregators

Conversation

@d4rken

@d4rken d4rken commented Jun 19, 2026

Copy link
Copy Markdown
Member

Restoring a backup taken on a feeder with no third-party aggregators — the common case — reported the aggregators section as failed and surfaced a "some items couldn't be restored" warning, even though the restore had fully succeeded. The backup intentionally records an empty aggregator set, but the import helper rejects an empty set with the same error code it uses for genuine failures, so that empty section was mistaken for an error.

An empty aggregator set now short-circuits to a skip before the import helper runs, so a clean restore reads as clean. Only a well-formed, genuinely-empty backup is skipped; malformed or populated sections still go through the helper, which owns structural validation.

Restoring a backup made on a feeder with no third-party aggregators
reported the aggregators section as failed and raised a "some items
couldn't be restored" warning, even though the restore succeeded. The
import helper rejects an empty set with the same code it uses for real
errors, so an empty set now short-circuits to a skip before the helper
runs. Malformed or non-empty sections still go through the helper.
@d4rken d4rken added the bug Something isn't working label Jun 19, 2026
@d4rken d4rken merged commit 8524df4 into dev Jun 19, 2026
7 checks passed
@d4rken d4rken deleted the fix/restore-empty-aggregators branch June 19, 2026 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant