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

If last message is displayed, the cache upgrade wasn't working because
we only checked from sending to sent, not sending to displayed and
status was lost after a reboot

Change-Id: I5d11e7560edf000e6fd9b8d3173d660baf0cc944

Change-Id: I2a7b5bebf350577203739b34c0487b5d720010a5

Change-Id: I22affb5cc4e97b2a1b6137d1f6e52262fef5b788

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

Change-Id: I87e9a81028e5a90490e263aee54e6f367a176c97

GitLab: #968
Change-Id: I9049d376984d480f686a369237b8dcab29144f45

In a class definition, the template deduction is failing.

Change-Id: If725c6a076fc4ac07ab0cf493959e51820abdc85

Change-Id: I87660a117c9f1c45c1066ddeb15c01e0e504b744

So that client calls getConversations() with an existing convModule_

git.jami.net/savoirfairelinux/jami-client-android/-/issues/1588

Change-Id: I8e7e3add0076b8d4b63a99c2ece29fd53b5c55d9

Change-Id: I2a7b7cc13268be127a6afe3d689d005b6596a3cd

Change-Id: I0aacf47c70a0de4fcd1a68f6688cf0ee0c551934

Change-Id: I7aedd81b133985210cf817d2c524ef3415a219c0

avoids deadlock

Change-Id: I01521a3e8c3da5774325dfcc78a96be6bd683fd4

Change-Id: I9a2ec38049a3b2e5dcbd04c3ca84e595e69a4e72

Also don't install pywinmake from the CMakeLists.txt.

Change-Id: Idf77fa95e1166561c809fba50b867a07d3358a83

Change-Id: I6c783563a0a58327012a3e2889ea78ea6c595d89

This is necessary in order to support screen sharing on Wayland because
the version of PipeWire that comes with Ubuntu 20.04 is too old.

Change-Id: I67bdd579d1496b66d014488a507fba06a8e7f683

Now, a client should not do any logic and not store preferences
client side.
+ When a member is removed while banned, the typing indication
is updated
+ Timeout is computed both for sender and receiver
+ Sending and receiving a composing status is managed by the
account's config.

GitLab: #951
Change-Id: Iba9441736eec4f71695bfbd609d4b9e8b6adcb73

This should fix sporadic failured in ut_conversationMembersEvent

+ A banned member get a valid conversation still on the device.
+ Re-adding a contact updates the "removed" state
+ Avoid useless network operation if we're removing and fetching
at the same time

GitLab: #956
Change-Id: Ife3678d2ba35cb5ca61c8f22c64aa3400eae23d3

If no commit is fetch, no need to forward the message

Change-Id: I1311a15d8ab81cd0b84ecce6a81a9398c239d938

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

The state is now partially observed by the jami core even
when the client is not subscribed, so we need to retransmit it
on subscription.

Change-Id: I6fc4b72b561b6fbd5f5ba6a9fa83a04d9914088c

For backward compatibility with jami versions that do not yet
send a conversation ID in the request, this patch adds the option
to load all conversations.

Change-Id: I0764d46c635aa3dd05be7adc991918ff53f2c673

Change-Id: Idb5ddd8471e30fd31ebb48f495537d10b24ff250

Change-Id: I6c892f0667bf4c2a7122297b7523f756baf20a8f

Change-Id: Ie52a0f0c0b499d22caa03714741e9bca96839fac

Change-Id: I89e11e723ab0cc53c8e025bb9aa4a0b8322ec82c

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

We recently changed getContactDetails() to get the removed state when
needed. However, getOneToOneConversation was now returning a removed
conversation causing the request to be ignored if both sides removed
them previously.

GitLab: #1619
Change-Id: Ie7464460609d6c1b6b3774318fb50116b7408f0a

Change-Id: I43a682cbd6a4bf26065f325b61330d03a8f68497

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

Change-Id: Icb82f42449478e632a4fe97a05c57533f564f42b

Use member event signal to check if a member is removed and avoid
merge id

Change-Id: Ifc18d5e12594bedf2f47bbc5d6d88a9c0dfbd6c7

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

dht_ can be nullptr. Moreover, configurationMtx_ should be improved
but for now ,this will fix the crash

Change-Id: Id6554a679d6397ba83d5026b8a8d9eadc6c882ee

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

Sometimes, failed wasn't called

Change-Id: I7734518a5d186b45a6d82da14bd20948ec0976f9

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

This allow unit test to be able to check why a call is declined and
allow client to clarify messages for call messages

Change-Id: I37f8f1d1160910ca702010e4a9a40c9ecbcd13fd

Change-Id: I65ca8d0fc907b8a4dea2cebe459ac67d0ba21f5d

There were no useful test as it duplicates test for ICE connectivity
and doesn't test media

Change-Id: Ifde558bf44bbd60911385760c209eb4ccab9dc12

There was both "Account.dhtPort" and "DHT.port" in the config and
this was unused.

Change-Id: I5a21b20923e8d588e6be52eb9e89f40a46836890

Change-Id: I30e0a693dcaa3e88df579b6e794be9b2de9b147c

Change-Id: I802152553dae070fd0e1d2cfb6d5a0259ff1a3d5

Basically, the user must override the values in the config, will
be done via jenkins for our CI

Change-Id: I6908f116f194444ae76b2843cd5795e94342a922

Green indicator is not understandable for the majority of users.
This patch introduces a new approach to this status. API doesn't
change, so this is 100% backward compatible but introduces new
possibilities:

1. The status sent to the client is now 0=offline (no device found
on the DHT), 1=dht_presence (at least a device is found on the DHT),
2=connected (with a TCP + SIP channel, so ready to exchange data).
2. Publish can now be used on a Jami Account. Status is ignored,
but custom note can be added. e.g. "Lunch time!"
This status is sent via a PIDF XML status as described in RFC3863
(and already supported by SIP account) to connected peers (or for
future connections).

Several scenarios are tested in ut_presence

Change-Id: I87d987bc69e97f92a0c9f4751069e52ad69ea0fc

This avoid to log commits at startup to get initial members() and
speed-up a bit load conversations

Change-Id: I402ee32bac19261e937b5cd8e738122619952cdb