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

Commit 86d3bb66 accidentally broke two conversation tests by removing
necessary waiting periods.

GitLab: #1117
Change-Id: Idebd037b2bf9083f59a108455fea82f2203a3ece

GitLab: #1113
Change-Id: I0772167f692b8551c6009c7b8c1ae4f63cecb73e

Gitlab: #930
Change-Id: I76f07a81c4887d0dc127d74bc6c4de2e9f4f2ee8

GitLab: #1100
Change-Id: I6ae6d125c730fc9a8a2125b9b6da68c005922bce

Adrien Béraud authored 2 months ago and Adrien Béraud committed 2 months ago

Change-Id: I65c99d62848b2d18e5c54e7b8ec28219320fb363

Adrien Béraud authored 3 months ago and Adrien Béraud committed 2 months ago

GitLab: #1097
Change-Id: I742d1306007b3ae4908ee2d46bd5275d1ce2c99a

Change-Id: I2753c58c12d167ee5f7454e5a2ed893991c90e24

ovari authored 4 months ago and Adrien Béraud committed 4 months ago

cannot → unable to
fail to → failed to
{inexistent, non-existing} → nonexistent
P2P
try → attempt
UPnP
retrieven → retrieved
testAdminCannotKickTheirself → testAdminCannotKickThemselves
wishes → wants

Change-Id: I84dbb7b78fd674507eab7186c8f9e0a5f1d3d5b3

Adrien Béraud authored 4 months ago and Adrien Béraud committed 4 months ago

Change-Id: I06afa15ff33a639458a618364d4eb00197de585a

Léopold Chappuis authored 4 months ago and Léopold Chappuis committed 4 months ago

If another key includes "PHOTO" during the API update process, it must be removed.

Change-Id: Ic338263ec3966556c61e12752ccea91fb730b794

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

Change-Id: I8b9e25f99da5945684e265d3923b74065c8ef8eb

Andreas Hatziiliou authored 6 months ago and François-Simon Fauteux-Chapleau committed 6 months ago

Fixes the issue where one of the daemon-tests would repeatedly
fail. Cause was an expired plugin certificate.

GitLab: #1015
Change-Id: Ib6059402569c9817514e3a80dad63b3c52c1e3c1

ovari authored 7 months ago and ovari committed 7 months ago

8+3 filename → 8.3 filename
be ware → beware
{cannot, can not, cant, can't, could not, couldn't} → unable to
conpleted → completed
file name → filename
imcomplete → incomplete
informations → information
trying to → attempting to
wrong password → incorrect password

GitLab: jami-client-qt#1730

Change-Id: Ia7757efafd2c06af978db02c65b40b1b77c393f8

François-Simon Fauteux-Chapleau authored 8 months ago and Adrien Béraud committed 8 months ago

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

Second part of this fix: https://review.jami.net/c/jami-daemon/+/28337
GitLab: #1721

Change-Id: Ie428a57d89ac3db4e32660735cb3a5b0bf0f5c94

jami-client-qt#1804
Change-Id: I8cb3ffc7d5b1b2b8bbfe018b922c260a569411fb

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

GitLab: #952
Change-Id: I50264953b3d1575cc323caf5348747f8b8a35313

GitLab: #972
Change-Id: Ic345e31ff51c9d51b50df0c911594e9d7f07ebbb

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

Change-Id: I80fb049e0c4e70005c844deed1cf35ed868a2293

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

GitLab: #958
Change-Id: I91036c9f1e20ee19e3896eb8e0110aa36a9d0602

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

Change-Id: Ieede07472435b7f8ae0b19a0ec2afad94e195fee

Change-Id: I5576412901a12be74395823a6abf7954bbd72b73

Amna Snene authored 1 year ago and Amna Snene committed 11 months ago

certstore test and ice test are moved to DHTnet project.

Change-Id: Iefba61c36d5790df5753fefd97b0eaa40f15ad0d

+ 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

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: I22affb5cc4e97b2a1b6137d1f6e52262fef5b788

GitLab: #968
Change-Id: I9049d376984d480f686a369237b8dcab29144f45

In a class definition, the template deduction is failing.

Change-Id: If725c6a076fc4ac07ab0cf493959e51820abdc85

Change-Id: I2a7b7cc13268be127a6afe3d689d005b6596a3cd

Change-Id: I0aacf47c70a0de4fcd1a68f6688cf0ee0c551934

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