GTest exports the following targets:

• GTest::gtest
• GTest::gtest_main
• GTest::gmock
• GTest::gmock_main

This targets should also be available when adding gtest with add_subdirectory (or FetchContent), because this should behave the same way as adding GTest with find_package. So somewhere, we should add the aliases to these targets, i.e.

add_library(GTest::gtest ALIAS 

The test coverage is currently visible on Coveralls. At the time of writing, coverage is 68%. Not too bad! Ideally, we could be somewhere in the 80-90% range.

You can see cover

Currently there is no explicit way to "refresh" the alerts list or the alert details view, to view the most recent data. Unless you make some UI action on the page, the data will never be updated, once it's rendered.

You can implicitly refresh those pages with current data by performing some other action on the view:

• on the alerts list, you can switch from the the "Alerts" tab to the "C

When creating or editing a relationship, we should group the relationship type list with the same tag as on the contact page (Love, Family, Other kind, ...), i.e. with an element.

In Docker I can do this:

docker system prune -a --force --filter "until=48h"

which I use as part of a systemd timer on our CI server in order to clean up disk space.

However, when I try this

podman system prune -a --force --filter "until=48h"

I get an error saying Error: unknown flag: --filter.

The filter option was added to image prune and container prune in #

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in

Please see the picture below. I can directly copy the commit id through this button in Github. Does gitea support this function?