Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • windows_ci_static
  • cpack
  • windows_ci
  • cert_pk_id
  • proxy_push_result
  • cnode_put_id
  • update-windows-build
  • proxy
  • resubscribe_on_token_change
  • actions
  • client_mode
  • llhttp
  • search_node_add
  • crypto_aes_gcm_argon2
  • ios_notifications
  • log_fmt
  • v2asio
  • fix-msvc
  • message_split
  • v3.4.0
  • v3.3.1
  • v3.3.1rc1
  • v3.3.1rc2
  • v3.3.0
  • v3.2.0
  • v3.1.11
  • v3.1.10
  • v3.1.9
  • v3.1.8.2
  • v3.1.8.1
  • v3.1.8
  • v3.1.7
  • v3.1.6
  • v3.1.5
  • v3.1.4
  • v3.1.3
  • v3.1.2
  • v3.1
  • v3.0.1
40 results

src

  • Clone with SSH
  • Clone with HTTPS
  • François-Simon Fauteux-Chapleau's avatar
    François-Simon Fauteux-Chapleau authored
    When removing a contact, we need to update the ID of its linked
    conversation (to be empty, which is the convention used to signify that
    a contact doesn't have a linked conversation).
    
    This used to be done via the updateConvForContact function, but there
    were two issues (which are fixed by this patch):
    1) if the user had multiple one-to-one conversations with the removed
       contact, then the function would be called multiple times (once per
       conversation) even though the update only needs to be performed once;
    2) more importantly, if the contact's linked conversation ID didn't
       match any of its one-to-one conversations, then the update would not
       be performed at all. (Every contact should normally be linked to a
       valid conversation, but this can fail in practice due to
       synchronization issues.) As a result, the contact would remain linked
       to a conversation that no longer exists.
    
    jami-client-qt#1673
    jami-client-qt#1804
    
    Change-Id: Ia75c5b27a4120bc48da5f449a874354326c6d96a
    8f2b6d3f
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    Name Last commit Last update
    ..