Klemens Böswirth

How would I know what needs to be fixed? Without trying to implement the fix myself, I have no idea what needs to be done. If I had to guess...

The `backend` plugin just passes through the return value. So as I suspected, we need changes in `libelektra-kdb` to handle a new result for the `resolver` phase. Also the problem...

The stuff that is mentioned here is done.

You just need to make sure to only use a cascading keys as the parent key that is given to `kdbGet` and `kdbSet`. I assume, you simply use the key...

To explain this a little bit, if the parent key is not cascading, then only mountpoints with the same namespace will be considered, since other mountpoints can never contain data...

Is there a reason, we didn't end up using the `close-issue-reason: not_planned` option?

Yes we switched to the GitHub stalebot action. But I don't see the `close-issue-reason: not_planned` option in https://github.com/ElektraInitiative/libelektra/blob/master/.github/workflows/stale.yml. That means the bot still closes issues as "completed" not as "not...

No idea, @lukashartl or @markus2330 might know, but I'd just rerun the pipeline and see if the problem goes away.

> why does this link check fail? If a link works locally for you, always attempt re-running the CI job (with the button on GitHub). Link checker issues are often...

May I ask why you want to remove entirely remove the plugin? IMO (a biased opinion of course) the changes outlined at the top of this issue would have a...