The RING_ACCEL macro was not defined when compiling the unit tests with
the JAMI_VIDEO_ACCEL option enabled, which caused a heap buffer overflow
when running ut_media_decoder and resulted in the test failing in CI
with a "free(): invalid pointer" error.
GitLab: #1124
Change-Id: I333502a570224d9dd52a2b4e5e8ebe86d96e41a6
Modifies the Portaudio layer to listen for device list change
events and react accordingly.
Gitlab: #1120
Change-Id: Iba21ec5baf02fc8377923d6085e496e142ceac07
When a notification is received, the account should be
registered, regardless of whether we need to load conversations.
Change-Id: Icb68605d0b7bbee94ce4b49ba34e9ff878c66215
It seems that msvc doesn't support using the '+' operator to concatenate
an std::filesystem::path and a string, but that the '+=' operator works.
GitLab: #1118
Change-Id: I153b47458c5ec8c690cea9cd173c9054b115090d
When experiencing connectivity changes, a users registration
state might be ERROR_NETWORK, which would cause the message
not to send. This caused an issue with usage of jami over
a local network. If a device would disconnect from wifi/eth,
the various channels they had open with other local users
would keep alive but messages could not be sent.
Change-Id: Id3219fce31545b8102e9589b82aad32968d50f64
We already do this on Windows, but the Linux build has failed at least
two or three times in CI in the past year due to git.videolan.org being
temporarily unavailable.
Change-Id: I78bb1d147ee469d188789ee5268e219d811108e2
This patch fixes the conversation Id used when creating
conversations from iOS notifications extension.
Change-Id: Ifcf6c414b978e12aa1d7c5f4bd34536a07b7137f
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
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
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
Some of the unit test executables had different names depending on
whether they were built via CMake or Autotools.
Change-Id: Ie09ba448e0101035e69d95fc639a8bce0251759b
The CMake option to build OpenDHT's documentation was already disabled
on Linux but not on Windows.
Change-Id: I66b29e68cc64596ca3066122c27facd871620d05
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
