Change-Id: I351016eecacd9357b4b0ad54adacbcd8d39f8731

Change-Id: I86e4cc0da21d7def58823abc6e0e6bee71a0cfa7

Change-Id: Id2ffcdc6f7db9ecba4ee86c939de1a7ea30df2c6

François-Simon Fauteux-Chapleau authored 1 year ago and Sébastien Blin committed 1 year ago

The timeouts were due to the fact that the blocking_tcp_connections
option of the upnp library is enabled by default.

GitLab: #21
Change-Id: I1ba27983b2a583f022ee5daf1c9acedfcde73f96

Change-Id: I2a7b6d31cec1ae0a46084279a0c76f4a7ca40f50

+ Use a std::set instead a vector so that no duplicates is possible
and reduce the datas
+ Use unpacker to avoid "insufficient bytes" error on unpack
+ sync with server when removing a syncing conversation

Change-Id: I17f37a8cae2cf5424708010e3b5f132965ff5f2d

Change-Id: I74dd3db0aeab65ea3708b3616b62faa742ffb879

Change-Id: I74f9ec6e69d2de0da7a589e013b9c3f3f29382ce

Decrease lock number for case when contact not found.

Change-Id: I8eea57f73a491624ca2397d2d8efd63c6acccfcb

Change-Id: Iee22b03bf0b5171ed4dd5b6e8e26fea57e0022bb

Jami crashes on openSUSE Leap 15.5 due to a segmentation fault in gnutls
3.7.3.

Change-Id: Iba3705b48c7f5817eb644bab1cbf84d4536d6d04

Change-Id: I69eedb1f85d6a712ef7e8d2cd40b24a4416ca3d7

* handle case where linkFile == target
* hanlde case where linkFile already exists
* keep link if it already points to target

Change-Id: I01bd866332a29847d787cf55c6d1b8925c02b41a

Change-Id: Iee0494e053a2e897ab1849f5deaeb240f9cc5a6f

URI was illformed, scheme is intended. Now it works for both
jami and sip accounts

GitLab: #947
Change-Id: Ifc8d88be1cec91428dd8060c3c4e12efc55243f0

Change-Id: Iec90e9d91f933531a96d4e84e6a3ed242caf1422

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

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

Andreas Traczyk authored 1 year ago and Sébastien Blin committed 1 year ago

- refactors uriFromDevice to always use a cache
- clang-formatted; relevant changes are:
  ~conversationrepository:269
  conversationrepository:2421

Change-Id: I938dbb73e7ee70304aa54113cfeb6ca00efa1265

Change-Id: I199352d8f01ded265d7199d1e087e12d71ed50a5

Change-Id: Ib2e4ffa708c60f49109aa2d4eddb9317ed6a27a3

GitLab: #944
Change-Id: I6ca19f941cdcb17e68532ba9e826f24c9692e512

git.jami.net/savoirfairelinux/dhtnet/-/issues/19

Change-Id: I25202099b6dc5e07606b2d66a35f966576659ccd

https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1519
Change-Id: I728a7fa4b59d949c350949308af1aaf045043338

GitLab: #943
Change-Id: I6f011053278bd2d3016e390c281f1cf47dfeac79

GitLab: #942
Change-Id: Ifdd50fc15695123f5ec41cb3eabb3a23b79e85dc

GitLab: #941
Change-Id: I35f467a242d22c41f1a640ee751478532f988ccb

Change-Id: I5139977d9d1fe49c9773ab3ad4a069ecf67ef637

Change-Id: Ia6d5e2c8f211e5206dec214232c929e624c307de

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

Change-Id: Ib7b61be24c94d79ef426a2c93021188b6dbae040

Change-Id: I683893b12f5055993ed12ae8ed89572a8bbf5dad

Change-Id: I3972fce8310cc4f6b5b6891e369e73197e8260b0

Change-Id: Ibeb67458e76cf413a53120fe3382bf625c7f0de8

GitLab: #937
Change-Id: Ie5cb7dc74b593d4107b5d22f8954f6dcd412c4f6

Alexander Lussier-Cullen authored 1 year ago and Sébastien Blin committed 1 year ago

GitLab: #831

Change-Id: I8e2aa205629735df043618a87e54ae6a43e6ca3f

Change-Id: I263e3057efb3aef103b3de367d9f2d0e03d5b368

Change-Id: Iabfc904e5c48a2fb17c7aa1b5467b36359c8d12c

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

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

if (acc && isOneToOne) the lock was unlocked before
addConversationRequest

Change-Id: I670dadf806ff2c949d8260c83cd9cce42ab1b3d6

- fixes crash
- clarifies a method name that operates on multiple commits
  convCommitToMap -> convCommitsToMap

Change-Id: Ia37a02fbb8c4ef9d349cf7d4ec4663f4bf7a7416