-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer
Milestone
Description
Currently when a new runspace is created its default name is "Runspace#". The only exception to this is the runspace created on a host process for IPC and it is named "RemoteHost".
We should provide runspace names with meaning when possible. This would make it easier for users to determine which runspace in the list is the one they want to examine or debug.
For example:
- The first runspace created in a session with a PSHost should be named "HostRunspace" (now it is "Runspace1").
- The IPC host runspace should be renamed to "IPCHostRS".
- The runspace proxy created for a WinRM remote session should be "WinRMRunspace#".
- The runspace proxy created for an SSH remote session should be "SSHRunspace#".
- Internal runspaces created by the PowerShell engine could be something like "InternalRS#", or "PSTempRS#".
- Workflow runspaces could be "PSWorkflowRS#".
lzybkr and 3xcharm
Metadata
Metadata
Assignees
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer