GitLab

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

still needs a property to switch between tree and flat modes

Otherwise we get unexpected sensors appearing when a new device is
connected. This is currently mainly triggered by the network plugin that
shows/hides devices based on connectivity.

According to the `man 2 nice`:
The range of the nice value is +19 (low priority) to -20 (high priority).

BUG: 426774

Needed for future power plugin

GIT_SILENT

This reverts commit 74992528.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

The current state is an example of good enough but not correct. There were two
issues. The first one is that I accidentally used the wrong kind of brackets.
Secondly we need to  escape only after matching because the name could contain
escaped dashes.

GIT_SILENT

GIT_SILENT

GIT_SILENT

setSensorId only connects when the sensor is enabled, which means we may
not yet be connected if the sensor is created in a disabled context.
Rather than always connecting, make the connections explicit only
enabled when the sensor is enabled, so we do not do unneccessary work.

Sometimes the CGroup gets deleted before the Runnable finishes, causing
a crash when we try to lock the PID lock. Since we have no way of
tracking the CGroup object lifetime, rework the code to instead have the
CGroup wait on the runnable when needed. Effectively this turns the
runnable into more of a Future.

QString::mid() return a temporary QString. QStringView doesn't actually
hold any reference to data, so the temporary gets deleted somewhere
after we create the string view, which makes the string view invalid. So
instead, use QStringRef here for which there is a separate method.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Otherwise we end up sending stuff like SIGILL when we want to send
SIGTERM.

QAIM::data is used by QML, which cannot handle a QVector<pid_t>
properly, so make sure to expose a the list of PIDs as a proper
QVariantList.

We still need to update the history even if it has the same value as before.
Should fix the unit test on FreeBSD.

As it turns out, smaps/smaps_rollup are fairly slow to read because the
kernel iterates all the memory of a process when this file is accessed.
This caused the update time of all processes to go up from ~30 ms to
more than 200ms.

This changes things to do the reading of smaps_rollup in a separate
thread that doesn't block the main update. This reduces update time to
~50ms, which is noticably better. To accomodate the asynchronous nature,
some additional functionality needed to be added so we can notify
Processes of the asynchronous update.

It's unused and no plans to use it in the future

In certain cases, a race condition seems to come up where the PID
retrieval thread tries to set the PIDs while the cgroup object is being
deleted. So lock the mutex in the destructor, so that if that should
happen, destruction will block while the PIDs are being updated.

Otherwise ConfigPropertyMap will still sync data, while we do not want
it to.

QThreadPool::start(std::function) was only introduced in Qt 5.15. This
adds a workaround (basically importing the class from Qt 5.15) for
earlier Qt versions.

The new threaded CGroup handling requires 5.15 so we should also require
it.

The network plugin changed the sensor ids of a number of sensors. To
support old configuration files, we need to translate these sensors from
their old IDs to the new. This adds support for that when loading sensor
faces and presets. In addition, when loading a pre-existing
configuration, it will write back the new sensor ids.

This allows us to access it from autotests.

The sensorId can contain characters which have special meaning in regexes. We
cannot escape them however because we also pass sensor regexes through the same
path. So simply compare for equality before doing any matching.

Prevents the Control from resizing and ensures there's click space also in a
very narrow layout (ksysguardqml) when the face allows two total sensors.

Makes it easier to see changes in formatting if we make changes there.

Makes it easier to select multiple sensors at once. The popup is automatically
closed if the maximum number of supported sensors is selected.

Instead, store the processes in the cgroup model, so we keep those
together. This avoids needing to keep track of which processes get
removed, instead we can just drop the cached processes when updating.

This prevents reading the cgroup files from blocking the main thread.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"