* handle case where linkFile == target
* hanlde case where linkFile already exists
* keep link if it already points to target
Change-Id: I01bd866332a29847d787cf55c6d1b8925c02b41a
If the first interaction from a device in a conversation is a
profile update, the certificate was not added correctly causing
the conversation to be illformed
GitLab: #946
Change-Id: I07f1735639c2dbf89ba2b2e6b7d9c3f57e5823e4
Because the encoded avatar can be greater than 64k, a SIP message
will fail, and the trust request may not be sent.
https: //git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1491
https: //git.jami.net/savoirfairelinux/jami-client-android/-/issues/1537
Change-Id: Ieba2db521a3c7e72890be75d3578f93e496dc968
loadMessages didn't return any linearizedParent because we were
passing a value to the client before the update.
Also, last message loaded will not have a linearized parent (because the
parent will not be loaded yet), so we need a message updated signal
at the next load.
Change-Id: I01c46f2c34be2131abd731eb745c203e50b95b9a
- fixes crash
- clarifies a method name that operates on multiple commits
convCommitToMap -> convCommitsToMap
Change-Id: Ia37a02fbb8c4ef9d349cf7d4ec4663f4bf7a7416
Group operations to avoid race condition. This fix sporadic failures
in testAddOfflineContactThenConnect
Change-Id: Id136c024be3eb3efe0f5430a4b64480f0ef10804
Else, socket can hang for nothing.
Moreover, erasePending is moved for the close to be removed as
soon as possible.
This fix sporadic failures in ut_syncHistory
testSyncCreateAccountExportDeleteReimportOldBackup
Change-Id: If230a780d3db93c6b37269a254e339c873fabe92
Bitrate adjustment (REMB) packets in video calls are sent back on the
same socket pair as the video itself.
Video being enabled or disabled should thusly not stop communication
on these sockets fully as they could still be needed for these packets.
Change-Id: I3789aae44884ad5acfe5e1b014767ff2bf84ba33
This heavily changes the API for the client. The goal here is
to move the logic to construct the history to show in the daemon
and not the client. This has several advantages:
1. Logic is common across every platforms, so bugs should not be
platform-specific
2. Client got less logic
3. Signal are simplified, if an edition comes, "MessageUpdated"
will be triggered instead MessageReceived.
4. Some tests are added for linearizing the history.
5. Search on edition is fixed.
Tests got heavily re-written, but the content didn't change (2 tests
are added, the rest is simplification).
GitLab: #831
Change-Id: Ie7c81077067e9e49db1dd396829c9225c0512c16