Summary: | Switching from lazy synchronization mode aborts remaining lazy sync | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | HubMiner <cal030> |
Component: | Maintenance-Metadata | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version First Reported In: | 8.7.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | 8.8.0 | |
Sentry Crash Report: |
Description
HubMiner
2025-07-25 03:16:21 UTC
Where is the bug here? If you re-enable Lazy Sync the queue is still available. Maik I assume most of the users simply won't notice that their lazy sync just got interrupted. If I start a lazy sync, I assume that's a guaranteed commit operation that will run to completion, it should not be susceptible to config changes. Sorry, that's nonsense. Then we also have to block changes to metadata write options when lazy sync tasks are pending, or any other metadata-related options. Maik |