Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • briar briar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 783
    • Issues 783
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Issues
  • #209

Closed
Open
Created Jan 07, 2016 by akwizgran@akwizgranOwner

Ensure clients can reliably respond to contacts being added/removed

Adding or removing a contact may trigger actions by sync clients (such as adding or removing a private group shared with the contact).

If the app crashes immediately after the DB transaction that adds/removes the contact is committed, event handlers registered by clients may not be run.

Possible solutions:

  • Clients could check the contact list at startup and perform any actions needed to bring their own state back into step with the contact list.
  • Clients could register handlers to be run in the same DB transaction as the add/remove event.
Assignee
Assign to
Time tracking