Bug 389609 - akonadictl fsck: optional show metadata for affected items to aid user to fix up things manually
Summary: akonadictl fsck: optional show metadata for affected items to aid user to fix...
Status: RESOLVED INTENTIONAL
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-29 17:10 UTC by Martin Steigerwald
Modified: 2018-01-29 20:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Steigerwald 2018-01-29 17:10:10 UTC
Akonadi 17.08.3

Ideally akonadictl fsck would fix up:

Bug 309474 - akonadictl fsck : item has no RID

Bug 389608 - akonadictl fsck: offer to fix duplicate items 

and other issues with Akonadi cache automatically.

Even better would be that Akonadi would avoid most of these issues the best it can.

But until getting there, in addition to have more helpful error messages (Bug 389607 - akonadictl fsck: Show more helpful messages) it would be good if akonadictl fsck would optionally show some metadata about the affected items.

Like in

akonadictl fsck --show-meta-data

and then displaying:

From / Subject / local maildir file (if known) for mails and so on.

Similar for other types.

Of course it would be better to automatically or at least interactively (by asking the user) fix up things so if you intend to go that route, feel free to close this one as WONTFIX. Or to avoid these issues from happening.
Comment 1 Martin Steigerwald 2018-01-29 17:11:06 UTC
This should be optional for privacy reasons. (i.e. when sharing with other users or in a bug report for help).

Metadata for mail probably should include Message-Id.
Comment 2 Daniel Vrátil 2018-01-29 20:24:37 UTC
This would be a major effort and something that's not easily achievable with the current architecture.

"akonadictl fsck" is a service inside the akonadiserver and therefore it has no knowledge about the payload format - IOW it does not understand "MIME" or "iCal" or "vCard" formats, it simply sees the payload as a binary blob.

At the same time, this tool cannot be easily re-implemented outside of the akonadiserver (so that it would be able to understand payload formats)  because it directly interacts with the SQL database, which cannot be safely done from outside of the akonadiserver process.
Comment 3 Martin Steigerwald 2018-01-29 20:55:52 UTC
Okay, Dan. Considering your comment I think it is not beneficial to keep this bug report open. akonadictl fsck appears to be a developer tool and maybe users should not even use it. That leaves that Akonadi shall be able to fix up inconsistencies by itself, or avoid creating inconsistencies in the first place by using atomic operations and roll-back but that is for other bug reports.