[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Akonadi] [Bug 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
From:       Grégory Oestreicher <greg () kamago ! net>
Date:       2014-08-31 21:57:37
Message-ID: bug-335090-17878-Ks8W4M6in6 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=335090

Grégory Oestreicher <greg@kamago.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greg@kamago.net

--- Comment #30 from Grégory Oestreicher <greg@kamago.net> ---
Hey Ingo,

(In reply to Ingo Ratsdorf from comment #29)
> I had a look through the code and you seem not to handle error 412,
> "Precondition failed".

Well actually 412 and 428 are considered unrecoverable errors, so an error
message will be shown and the event not updated.

> This is now separate bug #338570.

Yup, I  saw this bug and worked on the conflict resolution tonight. Now it's a
bit tricky to get it working (at least I  couldn't) because Akonadi only
implement local/local conflicts, i.e. conflicts that happen when two items are
updated locally by multiple applications. The local/remote conflicts are not
implemented, though there's the idea in the code.

In the end I've tried to game the system by faking a local conflict but this
did not work out because the resource is never notified of the choice made by
the user and thus can't act accordingly (overwrite the remote item for
example).

Another limiting point is that the conflict handler is declared in a private
header that can't be used from the resources… I guess that the grunt of the
work must be in Akonadi to implement the local/remote conflicts management.
Actually I  have a lot of work to bring the bugs back under control, so this is
not a high priority, especially now that errors will be shown plainly, but it's
clearly something that must be worked on.

Cheers,
Grégory

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]