After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658266 - libsocialweb PersonaStores with 0 Personas never reach quiescent state
libsocialweb PersonaStores with 0 Personas never reach quiescent state
Status: RESOLVED DUPLICATE of bug 656184
Product: folks
Classification: Platform
Component: libfolks
git master
Other Linux
: Normal normal
: folks-0.6.2
Assigned To: folks-maint
folks-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-05 15:00 UTC by Raul Gutierrez Segales
Modified: 2011-09-05 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Raul Gutierrez Segales 2011-09-05 15:00:28 UTC 
I've got some libsocialweb PersonaStores with 0 Personas that never reach quiescent state:

Persona store 'twitter' with 0 personas:
  type-id               libsocialweb
  display-name          Twitter
  id                    twitter
  personas              Set of 0 personas
  can-add-personas      FOLKS_MAYBE_BOOL_FALSE
  can-alias-personas    FOLKS_MAYBE_BOOL_FALSE
  can-group-personas    FOLKS_MAYBE_BOOL_FALSE
  can-remove-personas   FOLKS_MAYBE_BOOL_FALSE
  is-prepared           TRUE
  is-quiescent          FALSE
  is-writeable          FALSE
  trust-level           FOLKS_PERSONA_STORE_TRUST_PARTIAL
  always-writeable-properties  {  }


which means the IndividualAggregator will (also) never reach quiescent state.

How do we handle such cases?
Comment 1 Travis Reitter 2011-09-05 16:45:32 UTC 
This is a specific case of bug #656184, so I'll just point that to this description.

*** This bug has been marked as a duplicate of bug 656184 ***