Ilya
It seems we need explicitly dispose the named pipe. /cc @PaulHigin What do you think?
@MaFreiberger Please open new issues with repo steps and examples (screenshots)
> I am running PS 7.1.0 final on OpenSuse Tumbleweed and I still see these files getting created in /tmp @JoeSalmeri They will always be created. A problem is if...
@JoeSalmeri Please see https://github.com/PowerShell/PowerShell/issues/11599#issuecomment-602720389
@PaulHigin Makes sense to open issue in .Net Runtime repository?
> The listener allows one local PowerShell process to connect and **debug** another PowerShell process. This is very convenient but is not needed all of the time, and on Linux...
> > If it is for debug it is not clear why this should be opt-out but not out-in. > > @iSazonov That will be a breaking change. Breaking what?...
If you look at the [comments](https://github.com/PowerShell/PowerShell/issues/11599#issuecomment-1177914178) above, not only on Unix, but also on Windows, this feature leads to destruction of the production process. As result _I don't think we...
I'm sorry that I mixed these two problems up. But the problem with remoteIPMoProxy_* is not completely solved. One example. ```powershell ipmo dism exit ``` It's just that this module...
> But before this feature is made `opt-in`, we feel some time should be spent looking into whether PowerShell could perform clean-up of the orphaned named pipe files on non-Windows...