This patch fixes a logic error in testCreateParticipantsSinks which was
introduced in commit 0757c2cf.
GitLab: #1132
Change-Id: I1c34857f5a309ee34dd976a9d91c3ef1ba938408
Add directives to use git_comit * const for final parameter when calling git_commit_create_buffer function using v.1.8.0, v1.8.1, and v1.8.3
Change-Id: Iffc023b0ae87f14aea15b360d00da76933a81cc4
As of commit 68fc552, presence notes are only sent to contacts (as
opposed to all peers the user is connected to).
GitLab: #1125
Change-Id: I454c6bc880a65ad99747169cfc020a7ea7329de9
The local cv variable in testSendMessage was shadowing the corresponding
member variable in SwarmConversationTest. As a result, the calls to
cv.notify_one() in the signal handlers had no effect and the calls to
cv.wait_for() in the test would block until they hit the timeout, which
significantly increased the amount of time needed to complete the test.
Change-Id: I75b6aac8801568831a17035ad86876a130efe12e
testAskToMultipleParticipants was failing because of a temporary file
that was generated by the previous test and not deleted at the end.
GitLab: #1126
Change-Id: I5a98d259ba974fe72ced94ca3ccecb611a60dc2a
Use a single static instance of Json::StreamWriterBuilder
instead of creating a new one repeatedly.
Move json-related symbols to their own namespace.
Change-Id: I5145a71d7b19fd2aac158b51774e964ce772311b
PluginsTest::testTranslations assumes that at least one of the fields in
the TestSuite plugin's manifest has a French translation. Such a
translation was added in version 1.0.1 of TestSuite last year by commit
d0e0ef18395a07a1579b512c5d67bf61f7c3587a in the jami-plugins repo:
https://review.jami.net/c/jami-plugins/+/25667
However, the daemon plugin tests were still using version 1.0.0 of
TestSuite, which is why testTranslations was failing every day. This
patch fixes the issue by upgrading the TestSuite.jpl file used for the
tests to version 1.0.1.
GitLab: #1064
Change-Id: I7b851083bd8e1ac80d61f721baabbc092b46c56a
Fixes the issue where one of the daemon-tests would repeatedly
fail. Cause was an expired plugin certificate.
GitLab: #1015
Change-Id: Ib6059402569c9817514e3a80dad63b3c52c1e3c1
This patch makes two changes to ensure that banned swarm members don't
sync with or receive message notifications from other members:
1) when bootstrapping a conversation, devices belonging to banned
members are no longer added to the swarm manager;
2) when merging a "ban" commit for a certain swarm member, that member
is immediately removed from the swarm manager's routing table and all
Git sockets with them are removed.
GitLab: #1041
Change-Id: Idb817795f978ca4ca46502efea5101831ffccbe3
This patch moves the updateConvForContact function from JamiAccount to
ConversationModule. This fixes a deadlock that sometimes occurred when
starting Jami.
GitLab: #1033
Change-Id: I441426fa339e5cfb327566df6132bfecb206bd1e
Else, if a client calls addContact with an invalid uri, it will
create a conversation with an invalid contact and the client will
be in a bugguy state.
git.jami.net/savoirfairelinux/jami-client-android/-/issues/1681
Change-Id: Id6227c45c279c78aac0a191b6ae688ebe0d3d1c4
This allow users to delete files. Moreover, change edited type and
use edited commit type instead.
GitLab: #796
git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1287
Change-Id: Ida04c15cf1570de2f7707ce547be9f4a5e638245
API changed for ut_conference.
For ut_conversation_call, because the host is not a dummy call,
we must change the hangup in manager.cpp and fix sink creation
for host while attaching.
Change-Id: Icfc296949438e92f7b9b986ed6aa3b463ec2334e
Now a conference can start without any call (this avoid to attach
a call without peer to create a conference).
Path is now clearer for a call creation:
+ If we receive a call, we attach it to the conference
+ Else we do not create any call and just attach the host.
Next step is to be able to attach a host in audio only without weird
tricks and group addParticipant/bindParticipant
GitLab: #953
Change-Id: I13785a5525e041c37fb62c0c9f355e9371f1e4ad
Also, start to fix audio binding (this will be a full patch, but
at least do not attach host)
GitLab: #959
Change-Id: I0aeb9121e2880a5afb4b1ca1a30710d1b60a2e7e
+ Avoid concurrent operations on same repository
+ Reset HEAD to always get a clean commit
GitLab: #931
Change-Id: If417c06934e2acab3382481718dc0bc46f40e3f9
If a conversation is syncing, conv->infos() is not available and
there is no conversation request. So we must keep metadatas somewhere
to be able to show profile of a conversation while syncing
Change-Id: If68e8476f456ab13a5523193d67bb1212e1cb46a
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
