Klemens Böswirth

SIGSEGV in MapRenderer

11

We are seeing an issue similar to #2206 in our app. The crash occurs a lot, but so far we have not heard from users that it impacts them. So...

Replace `Timber` with `org.maplibre.android.log.Logger`

4

Replace using `Timber` directly with `org.maplibre.android.log.Logger`. It looks like the few places where this is done is after the fork: https://github.com/maplibre/maplibre-native/blame/main/platform/android/MapLibreAndroid/src/main/java/org/maplibre/android/maps/MapGestureDetector.java#L506 --- **Orignal message:** **Is your feature request related to...

Expose isEnabled from underlying Sentry SDKs

1

### Problem Statement We do not enable Sentry in all our app's build configurations. If it is disabled, we hide certain parts of the UI. For this we use `Sentry.isEnabled()`,...

KeyError in set_power

1

With regards to the set_power function: This actually results in an error for me:  And then the Error Message (KeyError) ![Screenshot 2024-09-30 at 08...

Both `XcodeSeverityWriter` and `OSLogWriter` currently use ```kotlin throwable.getStackTrace().joinToString("\n") ``` to convert a given `Throwable` into a loggable String. This works, but it only includes the stack trace for `throwable` itself....

Precheck for 5.2.4 doesn't account for NOPASSWD

1

**Describe the Issue** This role is great and I'm incredibly grateful for all the work it has saved me. However, I found one small issue, with the way rule 5.2.4...

Look into adding climate entity support to the integration for UI benefits. First impressions: - Probably a good idea - How to deal with heat circuits, zone modules and individual...

**Describe the Issue** The check for 5.1.7 seems to broken when using `AllowGroups`. Possibly there is another reason, I don't quite understand how the check works. **Expected Behavior** After running...

**Describe the Issue** The check for 6.3.3.17 doesn't work, I assume because it tries to use `-k` instead of `-F key=` **Control(s) Affected** 6.3.3.17 | Ensure successful and unsuccessful attempts...

**Describe the Issue** The audit for rule 2.4.2.1 checks for permissions `0600`, while CIS only requires `0640` and https://github.com/ansible-lockdown/RHEL9-CIS only sets `0640`. **Expected Behavior** After running https://github.com/ansible-lockdown/RHEL9-CIS all audit checks...