Sven Rebhan

@abrekhov can you explain how this parameter can be used?!? It says "normally is should not be changed", so I wonder when to change it and where to find the...

@1tft and @PSHWorkShop, please test the binary in PR #15300 and let me know if that works for you! The new feature adds more than only querying the registry but...

@PSHWorkShop currently we use the name of the value returned by the function call. Your approach will run into problems if the method returns multiple fields I think, therefore I'm...

Yeah, there might be WMI calls that return more than one property (e.g. `EnumValues`) so we cannot autorename.

Seconding the comment of @powersj, I absolutely would want this linter enabled but having nightly OOM'ing often is not a good thing...

@powersj yeah we can do this, want me to change this to a `fix!(...)` and mark it a breaking change?

@powersj why did you lowercase the message? This is a log-warn and thus should start with a capital letter!

@tguenneguez thanks for looking into this and thanks for your contribution. I think using statefull PID finders (i.e. internal variables) is not a good solution because this has proven to...

@tguenneguez thanks for your thoughts! Regarding the naming etc, this should really be an independent PR! Regarding your concerns/objections: >This new good generates a compatibility break. The idea is to...

I didn't mean to suggest `pgrep` first. But no matter if you use pgrep or the native method there are two ways to so multi-criterion filtering: 1. Iterate over the...