Patrick Meinecke

I'm working on essentially rewriting the dependency (or rather the parts I use) that keeps introducing breaking changes. That should make it significantly more reliable, but it's taking some time....

ESCS hasn't broken in a while, so you can still get the feature there. Ideally ESCS could be shipped as an extension which would make getting it set up significantly...

@bergmeister It's kind of hard to comment on this in a way that is helpful. There are ways to make the state management more consistent but they aren't easy to...

> @bergmeister @SeeminglyScience I'm wondering whether the task we run these rules in should have a more general catch (right now we only catch `scriptRuleException`), which we could then run...

I'm definitely not suggesting a lock, but retry is not likely to be a silver bullet there. So `CommandInfo` is inherently unsafe to call from any thread that isn't the...

> It _is_ odd, and it means we (and the users) can't depend on `KeyChar` nor `Modifiers` in these cases. It looks like `Key` is at least consistently `OemComma`, but...

@JustinGrote is talking about the metadata attached to `ErrorRecord`'s. Basically when full error view is on it'll show the error line as the small anonymous script y'all create to call...

> @SeeminglyScience is correct, and this happens even in conciseview, not just full view Oh right, I forgot about the command name prefix until looking at the output and then...

@PaulHigin Enabling proper error handling only requires a few small changes: https://github.com/PowerShell/SecretManagement/blob/30991fd56ef43074c3ff76f303fbf35c9e46be7d/src/code/Utils.cs#L255-L271 ```diff param ( [string] $ModulePath, [string] $ImplementingModuleName, [string] $Command, - [hashtable] $Params + [hashtable] $Params, + [System.Management.Automation.PSCmdlet] $Cmdlet...

The Engine WG discussed this today, we're very happy to accept this change (pending review of course) with a few caveats: > Unnamed arguments in .NET are called argx Because...