Ignoring handles which are not in roster drop buddies from shared roster

[gdesmott]

For some reasons, ejabberd doesn't always properly update user's shared roster once we are connected but does send the contact's presence. Problem is, as PS discards presences from contacts who are not in the roster, the Buddy object is not created and so the contact is never displayed on the mesh view.

That's an ejabberd bug but we could workaround it by changing PS to accept contacts which are not in the roster.

[gregorio]

Hi Guillaume,

Is this shared roster work supposed to be in 8.2.0?

Can you tie it to some specific feature or capability that the user sees?

We need to decide if this is a blocker or not for 8.2.0.

Thanks,

Greg S

[gdesmott]

Yes, we still use the shared roster in 8.2.0.

Because of an ejabberd shared roster bug, user won't see some connected buddies in his mesh view.

[gdesmott]

I wrote a workaround in this branch: https://dev.laptop.org/git?p=users/guillaume/presence-service;a=shortlog;h=8444

I should do the job but add some D-Bus round trips. See the comments in the code.

[gregorio]

Is there any workaround (e.g. reboot) or way to know whent his will happen?

I need to figure out how to explain this in the release notes.

Also, is this only going to affect XS connected XOs?

Thanks,

Greg S

[gdesmott]

According my observations, this bug seems to happen when the user is already connected to the jabber server and then another buddy connects. It works fine when the buddies are connected before us.

[gdesmott]

This bug was fixed by this commit as part of the Gadget integration work: https://dev.laptop.org/git?p=projects/presence-service;a=commitdiff;h=ed0b5e3adc45a5127b16e63230edbc918ac54979

[mstone-xmlrpc]

Pushing out to 9.1.0, per edmcnierney's request.