[Kde-pim] Akonadi 4.13 testing issues

[Daniel Vrátil]

On Thursday 20 of March 2014 15:14:08 you wrote:
> All issues described are on a clean 4.13 beta 2 install and fully
> reproducible
> 
> 
> ISSUE 2: Authentication dialog blocks all Akonadi ressources
> 
>  If you have a ressource that can't log in on the server, it will block
> akonadi from accessing all other ressources.
>  This can be reproduced with Kmail: If akonadi cannot login on one server,
> you will be prompted a dialog where you can choose to retry/canel the
> operation. If you cancel, you can access all other resources again. During
> the dialog is shown, you cannot access mails of other resources that are
> available. This becomes problematic if the server takes long to report back
> that logging in was not successful, because it will make all other
> resources unaccessible.

It's not as serious as described here :-) It only blocks a session that 
started the fetch, not all resources. I'm experimenting with adding a timeout 
to ItemRetriever. There's a danger though that when there's a long-lasting 
task running in the resource (large collection sync), the retrieval might 
timeout, which we don't want, but I think that's a reasonable trade-out for 
locking up forever when a resource goes nuts or something.

Proper fix would be enabling parallelism in session and Resources, something I 
want to look in for 4.14 or Frameworks.

> ISSUE 3: Imap, Kmail Mail folder, and Mbox resources do not make use of
> "NotConfigured"
> 
>  Everytime you add a new Imap, Kmail Mail folder or Mbox resource, you will
> get a "Broken resource" notification.

I fixed the IMAP resource few days ago and Laurent has fixed the maildir and 
KABC resources.  

> ISSUE 4: Akonadi resources do not go online automatically, if Akonadi is
> started when there was no connection
> 
>  If Akonadi is started and there is network connection, all resources are
> online as expected. When you turn off and on the network access now, the
> resources go online instantly after there is network connection again.
>  But if you disconnect from all your networks, stop akonadi, and start
> akonadi using "akonadictl start", the resources wont go online themselves.

I suspect this could be because we don't detect the initial state of network, 
so when resource starts, it is set online by ResourceBase, and then it when 
the resource implementation tries to connect, it finds out network is down and 
sets itself offline, which overrides network detection in ResourceBase. I'll 
fix it tonight.

Cheers,
Dan



-- 
Daniel Vrátil | dvratil at redhat.com | dvratil on #kde-devel, #kontact, #akonadi
KDE Desktop Team
Associate Software Engineer, Red Hat, Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20140320/55d16a84/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/