This avoid the TlsSocketEndpoint to use an invalidated ICE.

GitLab: #763
Change-Id: If89a70521e523e19c38fd61c20c483b89a9b6413

DRing::fini is currently unsafe for atexit.

Change-Id: If4643a5f5455190351c45eebad816cba5b8c642f

Change-Id: Ib595ab696edddd0271b85933b26c591b078ad21c

Causes issues with yaml-cpp. Reverting temporarily until we fix the issue.

Change-Id: I2df0823554ad87880bc965bdff4f4707a6129789

+ search method was incorrect if no type provided
+ some tests were not waiting for correct signals

Change-Id: If6ba59829defb168f51c4a8e25f2054cd649b8c2

Vladimir Stoiakin authored Aug 24, 2022 and Andreas Traczyk committed Sep 08, 2022

Change-Id: Iceae2a19ce3febce62f7916af8b4242e06a7e1d4

Change-Id: Ifc2d7853ba58311356a4c33e80987424f3bff283

Change-Id: I238f452f77e10c16ebc5f69bef1b768f44e57e2e

Fix x86_64 build on Apple silicon.

Change-Id: I233a1e4f48d52a5f9dc56090c864c957a69a2221

Seems that JSONcpp symbols changed between 1.7.4/1.7.6 causing
some versions to fail.
We already uses 1.9.3 since a long time on other platforms
and ubuntu 22 got a version recent enough too.

Change-Id: I21a4c44ee1359a7d89e45770cb2bad9f2eb00cce
GitLab: #824

This clarify the UI to know what message was not synced with
someone.

Change-Id: If58b9858eaab4b9f161c5968e691c7fd5531ee97

Olivier Dion authored Aug 12, 2022 and Sébastien Blin committed Sep 06, 2022

These tests were never run on the CI and are not even in the build of Meson.

Change-Id: I0109633de2fd03b8589734d92c039b34d5b729bc

Olivier Dion authored Aug 12, 2022 and Sébastien Blin committed Sep 06, 2022

This test has not been compiled for a long time.  Even if fixed, the test does
not pass anymore.

Change-Id: I6e14cc42e1874962734c1592e47a780e04080a1f

Olivier Dion authored Aug 12, 2022 and Sébastien Blin committed Sep 06, 2022

This will setup the correct environment for each tests and echo tests that are
running.  Users can extend this with the TESTS_ENVIRONMENT variable.

Change-Id: I7aa0f04721251a6ea48cb4c2e7c2238f95d67267

Olivier Dion authored Aug 12, 2022 and Sébastien Blin committed Sep 06, 2022

Change-Id: I9c619d9492f3109e432a9803ae0a99cb2ab45d2c

Aline Gondim Santos authored Aug 08, 2022 and Sébastien Blin committed Sep 06, 2022

To apply translations, first try to read if the JAMI_LANG variable is
set, if not, try to get the system language.

GitLab: #747

Change-Id: Ie458abcc07c0d0fd151172e172fe1418e5f06e7f

This gives to clients the ability to perform search for messages
with several parameters (account's id, conversation's id, author,
period, max number).
(To discuss) This patch introduces the search API, and a signal
(MessagesFound) to return a result.

GitLab: jami-project#1382
Change-Id: Ibc4665449fa0da71a015d1d18d6d0d3209331d43

Change-Id: I384328c002aa1dc495e29dfa16ada3044cdeda28

Kateryna Kostiuk authored Sep 02, 2022 and Adrien Béraud committed Sep 04, 2022

This patch fixes crash that happened when block contact
for not active account.

GitLab: #758
Change-Id: I5347394a67cdffe0d95c9ee03aedf9d2618cec55

Olivier Dion authored Sep 02, 2022 and Adrien Béraud committed Sep 02, 2022

Change-Id: Ib91b2a994129b8dc63686d9ffc6f5166765e319a

Create a minimal test for the plugins system.

GitLab: #745

Change-Id: I17d48860ce24cfdc5423d4dcc3cb44bb4d4531f6

+ Some code were unused
+ Ask for profiles in one to one after a clone, this
allow to get the profile after adding/removing/re-adding
the contact as the peer will not know and got a cache
where they sent the avatar before.
+ Update unit-test

Change-Id: Ide1df647dbec63f343b60c1c622d1a214f4c3016

+ In jamiaccount, if a requestSIPConnection was failing, all subcalls
were stopped causing the main call to fail if not connected. In this
patch we only stop the subcall linked to that request.
+ In connectionmanager, if a request failed, we stopped all other
connections instead of just using the id of the request.

This fix calls whenever somebody called a contact right after the
contact changed its connectivity (and the keep-alive is not sent).

Change-Id: I0d9b14795aad37363de992cb29d4d4ca44668285

This allow to cancel the request if the connection is too long
(ipv6 un-resolvable for example)

Change-Id: I24757dd7a9893c36a86eccdc46271d5453205de5

This reverts commit 2f6f35cf.

Change-Id: I8b7d0b0fcccd010f03e1e29774ff9afe8e968452

EFETCH error should be given if libgit got an error, not upper
layer

Change-Id: Icdf08238573d435014e820cd63313a9d92381618

Change-Id: I8bdd1edef75f728464728644c159777e77d7f7d8

Change-Id: Ib857693a75dfa0f91e9deffd2a475ab97e27bd2b

Rounding the sample rate adds artifacts to the sent audio stream.

Change-Id: If82017c3cb69cb065ecfbdc5bfa96f2891874c25

This patch increase fetched conversation number earlier,
so ConversationSyncFinished would not be emitted in case when
second call to fetchNewCommits happened before receiving callback
from onNeedSocket_.

Change-Id: I72263768426fcce671029fd165323ce89e49e91b

Tobias Hildebrandt authored Aug 08, 2022 and Sébastien Blin committed Aug 24, 2022

Change-Id: Ie5c8fe1d9cc4e5a38a623a1cd4755c00ad4f4904

Several improvements are included with this patch:

1. confirmed is resetted when account is removed, this allow to
send a request when conversation is added back and reset the
whole matrix, avoiding duplicates
2. Banned can be due to harrasement. In this case, keeping the
conversation like the old behavior (pre-swarm) is better, to keep
proofs. Also re-adding back a contact is immediate if it was a
mistake as the conversation is kept back.

jami-project#1449

Change-Id: I13da8ce9bd431b91ce7b7d455dae561358c62f10

Removing a contact was not actually closing all connections, causing
the remote contact to be able to call even if it was banned if there
was more than two channels opened.
Rewrite closeConnectionsWith as it was unused to use it to close
connections with the banned contact.

jami-project#1449

Change-Id: I147f437370a553f0682b0cea060720a6c473f8a2

upper layer should not need to interact with the IceTransport
directly and only uses the API of the socket endpoint.

Change-Id: Iea65b03b37e87e9a7ab542ba88be5a2c6790ae98
GitLab: #703

Let the IceTransport layer stopped it's current read if destroyed
(as it uses a peerChannel, this channel should be cancelled to
let upper layer stop correctly all operations).
Call the shutdown callback whenever the ICE is really destroyed
(so caller must not re-use the ICE pointer).
Finally, remove some dirty underlyingIce() accesses in peer_connection

Change-Id: Icca73d9af273297a558121ffddc991ac6617ece2
GitLab: #703

This is a first version. This avoid "insufficent bytes"' errors due
to the pack with a max size of 8k (which can be the case)
In a future version, the SyncMsg will be splitted in partial data
to only use the necessary size and could take any wanted size.

Change-Id: Ic4b86a8ac8c3c49063e5650fefbb1f969b458db6

This patch updates libressl repo source, since according
to https://github.com/libressl-portable/openbsd/issues/128,
releases from libressl-portable could be regenerated.

Change-Id: If050a282341ccec76eb85ab78d44e10508b22f9d

We could recheck for the video device capabilities whenever the
devices list is requested. This can avoid having a virtualcamera,
like OBS, with mismatching information from what is available on the system.

GitLab: jami-client-qt#747

Change-Id: I012cfb71e12c8e9965b9d112e3ff0488c7cb285c

Virtual camera with non conventional fps where not working
properly due to a mismatch between the framerate rational in
daemon and AVRational in ffmpeg.

GitLab: jami-client-qt#478

Change-Id: Ida3a575be1dedae0e581257e38bf7469154a6ef5

Change-Id: I3eaa39c81fe816e3149ae8599fb8e95f84e18bc0