Recent testing with a Windows 10 machine has shown that the crashpad
submission timeout is too short. This commit increases the timeout to
10 seconds, as around 5 seconds has been observed in practice.
Gitlab: #1454
Change-Id: I557a414ea371bd94a42696a835370068867c99dc
Provide general improvements to the crash reporting submission services
by adding a separate report access server with a simple UI and updating
the crashpad submission server to use waitress.
- changes crashpad.py to crashpad_submit_server.py
- adds report_access_server.py
- updates README.md
Gitlab: #1454
Change-Id: I4e97f77cf2e2c0bb405064b0187ed3dfc2ee703e
This commit adds a basic crash-report system that can be optionally
configured to automatically send minidump crash-reports in addition
to product versions and a platform description including the OS
name and CPU architecture. Reports can be received at a configured
REST endpoint(POST). This endpoint URL can be configured using
a CMake variable `CRASH_REPORT_URL` which defaults to
"http://localhost:8080/submit".
- Introduces a new CMake option `ENABLE_CRASHREPORTS`, defaulting
to OFF. This allows developers to enable crash reporting features
at build time selectively. We also define a new macro with the
same name to expose the state to QML in order to hide the UI
components if needed.
- Implemented conditional inclusion of crashpad dependencies using
`ENABLE_CRASHREPORTS`. If set, `ENABLE_CRASHPAD` is also enabled
(other crash reporters exist and we may want to use them).
- 2 new application settings are added: `EnableCrashReporting` and
`EnableAutomaticCrashReporting`. Default settings make it so
crash-reports are generated but not automatically sent. With this
default configuration, users will be prompted upon application
start to confirm the report upload. Additionally, users may
opt-in in order to have reports sent automatically at crash-time.
Gitlab: #1454
Change-Id: I53edab2dae210240a99272479381695fce1e221b
The AppStream specification includes both a "metainfo" file format,
which can be used (among other things) to provide metadata about a
specific application, as well as a "catalog" file format used to provide
information about the contents of a repository. This patch adds a
"catalog" file for the Jami repos, which seems to be necessary in order
for some graphical package management applications to be able to launch
or uninstall Jami. In particular, this was an issue with GNOME Software
on all the rpm-based distributions supported by Jami (Fedora, openSUSE,
AlmaLinux).
This patch also fixes a few minor noncompliance issues with the existing
metainfo and .desktop files:
- the metainfo and .desktop files were renamed so that the names'
prefixes match the application's ID as defined by the <id> tag in the
metainfo file (in our case "net.jami.Jami") [1];
- the <br/> tags in the metainfo file were removed (they are not
supported -- metainfo files only allow a very limited number of tags,
not arbitrary html [2]); the list (<ul>) and list item (<li>) tags are
now used instead;
- the invalid categories "Communication" and "Productivity" were removed
[3, 4].
[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/AppData/
[2] https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-description
[3] https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-categories
[4] https://specifications.freedesktop.org/menu-spec/latest/category-registry.html
GitLab: #1842
Change-Id: I4a8bab79b6e54d02c08f509d7a9196a0a2e1541e
The current implementation of NotificationArea assumes that the
onActiveCallsChanged function in ChatView.qml will be called at least
once before the notification area becomes visible, but this isn't
necessarily the case.
GitLab: #1823
Change-Id: Ic85392dd9b6748b43f6c8d9cc002df973fc8be0e
Are you sure you → Do you really → Do you
by a password → with a password
confirmExtensionReset: OK → Reset
confirmExtensionUninstall: OK → Uninstall
confirmRmConversation → confirmLeaveConversation
Change-Id: I8e61197a19fb61f3d362d76b1a6d676dcb842b75
GitLab: #1730
- Give a hint on how to troubleshoot the contribs build.
- Add instruction for debugging runtime crashes using GDB.
Change-Id: I6ad931223ce0904fb292a59090d37a2cec422ae8
Since SIP accounts lack a URI, we need to address scenarios where the daemon includes the accountID in the uri parameter. Refer to 29623 for more details.
Change-Id: Ib58e77dc953269c87d67d4068866c93432d08aae
This change only impacts avatar updates; moving to the new API for updating the displayName is still pending and may require additional work. Specifically, we need to provide the current profile picture path to prevent its removal during the update process.
Change-Id: Idbc1592eda2b533b633cc366c72224f5e1bdce98
When creating an account archive, there would be no default
suffix. Then, when importing the archives, we would filter
for .gz files by name. The goal is to implement a .jami
file extension for archives across all platforms.
Todo: implement custom MIME type for custom icons.
GitLab: #1256
Change-Id: I202ae5670c928f35b0eaf711abf7249ec3f304b9
Sometimes qrencode failed when built from Jenkins.
This patch:
- Uses cmake for build.
- Automatically detect host architecture if none is specified.
Change-Id: I18dc90099e3b9efc531c7887b00fc615f69c50fa
No logic was implemented when you were alone in a conversation
(either conv with yourself or swarm with 1 member). This adds
the logic. Currently the receipts will change in swarms
if you add a member.
GitLab: #1867
GitLab: #1017
Change-Id: Iff2ea5978ac988d30edef32d803c0b5b70b11d90
There was a timing issue between when a new account is connected
and the moment where the avatar cache is cleared. Thus, the ui
would use the cache of the previous account for certain
conversations.
GitLab: #1832
GitLab: #1559
Change-Id: I0319b3d81e0b6dfec9b5408806dfd48ff220ea9d
The ContactModel::bestNameForContact function currently performs a
lookup on the name server every time it is called if its argument is the
URI of a peer which isn't a contact and doesn't have a registered name.
This patch modifies the function's behavior so that it doesn't perform
more than one lookup per peer, thus preventing the server from getting
spammed with large numbers of unnecessary requests.
GitLab: #1882
Change-Id: I7b7ef6a41d3db1001fc1418f8f35bd06b0932624
When starting a swarm call with video, the MRL for the host
wasn't set. Thus, the camera button would appear muted and
starting/stopping video would have unintended behavior.
GitLab: #1869
Change-Id: I6ee2204d5b49b856bfc72fb560f6623f9c7c874f
The goal of this patch is to make the messagebar (and more broadly
the chatViewFooter) more coherent in its behavior and look/feel.
GitLab: #1846
GitLab: #1848
GitLab: #1639
GitLab: #1420
Change-Id: I0d0ed207df9eba50f724c69fa49f956dc8aaa573
When the conversationview was resized horizontally to be small enough
so that only one pane is visible, the chatview header and footer would be visible, but clicking them would interact with the objects of
the pane below (the left side panel)
GitLab: #1868
Change-Id: Ic1fac91ef30fcc3078223e1705f10c8a112c2091
When searching for a user, if the user was found, a signal would be
sent to update the display name with incorrect formatting across the
application.
Change-Id: I20a453e2eddf1e1a402985ff741c8e7c7ea6f99f
Fixes an issue where the files that were loaded are not cleared
when switching conversations. Implements the correct behavior
for restoring the files as was done with text drafts.
GitLab: #1847
GitLab: #1528
Change-Id: Id04c9820d08f25ef247002da66d99ae893d8495a
Make it so that the reply/more/share buttons are visible
whenever the cursor hovers over the horizontal area
that a message takes up. Add message highlighting.
Fix small issue with "more" button not being deselected
after choosing an emoji
GitLab: #1870
Change-Id: I4db5230c2a50ce4640eececc69f8e88348356d79
This avoids merge modules which may crush system runtimes files. We've had several issues packaging vc_redist binaries also, so this seems to a better option for now.
Gitlab: #1865
Change-Id: I9ac3d3a1945136d7f78cf5be2de5d05cf377e126
