Change-Id: I765f7ebe02079ae91fa84e6fa7d54c9cfbada016

Adrien Béraud authored 3 weeks ago and Adrien Béraud committed 1 week ago

Change-Id: I940952e1f805a1a8bb3f3b0de9de626147e3c4e7

Adrien Béraud authored 2 weeks ago and Adrien Béraud committed 1 week ago

Change-Id: Ic282ac90339ecff26b8b195626059d2bf4f02d28

Adrien Béraud authored 3 weeks ago and Adrien Béraud committed 1 week ago

Change-Id: I1c8f8515998967c0e76173a8e65de3ef8e85343c

Adrien Béraud authored 1 week ago and Adrien Béraud committed 1 week ago

Use scoped environment variable names
for custom log levels:
DHTLOGLEVEL -> JAMI_LOG_DHT
SIPLOGLEVEL -> JAMI_LOG_SIP
RING_TLS_LOGLEVEL -> JAMI_LOG_TLS

Change-Id: Ic2dc29413382b5072a7aadb9356eb5b19514674d

Kateryna Kostiuk authored 1 week ago and Adrien Béraud committed 1 week ago

This patch fixes the conversation Id used when creating
conversations from iOS notifications extension.

Change-Id: Ifcf6c414b978e12aa1d7c5f4bd34536a07b7137f

Change-Id: I78dc58bd3c626b212f0527bb21efbd689cf93802

François-Simon Fauteux-Chapleau authored 1 week ago and Adrien Béraud committed 1 week ago

This patch is a complete rewrite of the algorithm used in the
addToHistory function to compute the status (SENDING, SENT or
DISPLAYED) of the added messages. This fixes a bug where some messages
would sometimes be incorrectly marked as being in the SENDING state,
even though more recent messages were known to have been SENT or
DISPLAYED.

GitLab: #1042
Change-Id: Ibfe0aeee57523348a5f8430492814572e607090e

François-Simon Fauteux-Chapleau authored 1 week ago and Adrien Béraud committed 1 week ago

The addToHistory function currently iterates over the list of commits to
add only once. This patch refactors the function so that the message
status computations are done in a separate loop from the rest of the
message handling logic. This will make it easier to fix a bug in the
message status computation in a subsequent patch.

GitLab: #1042
Change-Id: I3fceb10057292f84bc8c5e9d668fed7290ace8f2

When loading from the notification extension, check if the
conversation Id is empty. This can happen when cloning a
conversation or during resubscribe.
In such cases, we only need to start the account.

Change-Id: Ia59b88cbf00a594621b61a1d534b18cb3805c827

Change-Id: I4f39abfb8cba90b428554b1972cf6ed72b7682e5

Kateryna Kostiuk authored 1 week ago and Adrien Béraud committed 1 week ago

This patch validates the conversationId before proceeding with
cloning. Otherwise, an empty conversationId could lead to
accidental removal of the entire conversations directory.

https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1982
Change-Id: I428247498bb7533b12dadb8a479779e228e6dfb6

Change-Id: I29fcc7b078799abb3d8c5aba9a7bcb8f48357d2a

Change-Id: I5bc21822a8c754951a92ac7be8dd2e4af78cce6f

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

The LIBJAMI_TESTABLE macro was always defined, so using it in ifdef
directives had no effect.

Change-Id: I0f7ac906c70a90230cf224f9dc001712e1d5ca86

Preserve pre-std::filesystem behavior of returning null if operation fails.

Change-Id: I76414a73f8aa0a74640b92c27c753f0311d86380

Page Magnier-Slimani authored 1 month ago and François-Simon Fauteux-Chapleau committed 1 month ago

Rework the mutex lock to release it before the sha3 computation
to avoid a lock.

GitLab: #1919
Change-Id: Ic7f065959873bcc9f932e07611ed3c8010ef2979

Change-Id: I58ceec1d2c58b21f04aaa6a131a014d3b34a8d81

Adrien Béraud authored 1 month ago and Adrien Béraud committed 1 month ago

Change-Id: If05e5c35a739b7149b66622c249c303996ba8550

Change-Id: I8625be46bcde0c2f69f75cb341a11da7def7e0d0

Change-Id: I73eeb7a3c8f09e147a8ca2713028c94de6a72aa7

Change-Id: I3e8ccd71a1b5cb906b66837813bd132cc81f697a

Gitlab: #930
Change-Id: I76f07a81c4887d0dc127d74bc6c4de2e9f4f2ee8

Ensure the video muted state is properly maintained.

Change-Id: I69d768913e141eca820abe171732d855fc1d8a78

Use streamId as the media identifier since it is unique.

Change-Id: I68a0c8a53bdecdb22008260640fb79b6febd5b71

Adrien Béraud authored 1 month ago and François-Simon Fauteux-Chapleau committed 1 month ago

GitLab: #1110
Change-Id: I36e090fcb6c44b2483b1765786d64be108d93d21

Fix file access issues when reading hard links on Windows by:
- Adding explicit share mode (_SH_DENYNO) to allow reading files opened
  elsewhere
- Using binary mode to ensure consistent behavior with hard links

This resolves issues with reading hard linked files on Windows while
maintaining behavior on other platforms.

jami-client-qt#1899
Change-Id: I2adc0f29db46d5bf5b69762018e7a5e677ec3d04

For an account's VCard, we store the actual VCard file in the account's
profile directory, alongside other contact profile files, and a link is
created in the account's directory to the VCard file that is named using
the base64-encoded account URI. This method will fail on Windows where
users can not create soft links.

When linking to this VCard file, we first try to hard link to it. If
that fails, we fall back to symlinking to it. This allows the new
profile linking mechanism to work on Windows, and we are fairly
confident that the `profiles` sub dir will not be on a different
filesystem.

jami-client-qt#1899
Change-Id: I3be8150b02f8427c164beb6c652f96d895aab048

Change-Id: I6d88519a637c876848407b1e7b59e746b895c185

Change-Id: Iab22cafde6aa39a5dd970ace8de6150cc85e3bf5

Change-Id: I827de0a30a32e75e21993b435a0a68d71d846653

Add parseJson function to simplify json parsing:
* automatically log parsing failure
* allows single-line json parsing
* take a string_view instead of begin/end pointers
* optimize building the CharReader by reusing the CharReaderBuilder

Change-Id: I332a88fc476ee84ba400a96bc1b41515cca43c32

When removing a contact, we need to update the ID of its linked
conversation (to be empty, which is the convention used to signify that
a contact doesn't have a linked conversation).

This used to be done via the updateConvForContact function, but there
were two issues (which are fixed by this patch):
1) if the user had multiple one-to-one conversations with the removed
   contact, then the function would be called multiple times (once per
   conversation) even though the update only needs to be performed once;
2) more importantly, if the contact's linked conversation ID didn't
   match any of its one-to-one conversations, then the update would not
   be performed at all. (Every contact should normally be linked to a
   valid conversation, but this can fail in practice due to
   synchronization issues.) As a result, the contact would remain linked
   to a conversation that no longer exists.

jami-client-qt#1673
jami-client-qt#1804

Change-Id: Ia75c5b27a4120bc48da5f449a874354326c6d96a

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

Change-Id: I480edbe0fb14f4b4758a681fb789cb30385d4982

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

Removed legacy code that was causing options to be cleared unnecessarily.

Change-Id: I02b32221acc6abfef634ba843549c6391c2058c8

GitLab: #1101
Change-Id: Ifaee9fe0a2b79716e00ccc1a12c8c78c348e80bf

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

GitLab: #1104
Change-Id: I8d5c0a1fdb2f9bfc84f442e1323216ae3100da6d

Given the change made in commit
e048f1b9, it no longer makes sense to
use a null pointer as the default value for the optHistory argument of
the addToHistory function.

GitLab: #1102
Change-Id: Ifc5ca8b069c16d7d9cca2cbc0c8237c56895ff4e

Change-Id: Icd57e9a33b58c97ef9df18531510fb9590a9ee73