You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PowerShell console messages are not displayed with correct order. This issue happens with a lot of cmdlets but some cmdlets(ex get-process/get-service) work well. For example, run the following script. You can see the messages shown with wrong order. I know 'Out-Default' is called internally from most of get-xxx cmdlets but it looks like it does't work in some cases. I think console messages should be displayed sequentially with correct order because 'Out-Default' is called internally. But actual behavior is not(Out-Default is called but the message is buffered and not displayed). So please check if this is a bug or by design with host message buffering.
The output messages are displayed in powershell console/ISE with the following order.
Before get-acl
ディレクトリ: C:\WINDOWS
Path Owner Access
---- ----- ------
system32 NT SERVICE\TrustedInstaller CREATOR OWNER Allow 268435456...
After get-acl
Enter something:
Actual behavior
The powershell console/ISE shows the messages in wrong order like this. The output of get-acl is buffered and not displayed and message of Read-Host appears prior to output of get-acl.
Before get-acl
Enter something: <---- Should be displayed after output of get-acl
ディレクトリ: C:\WINDOWS
Path Owner Access
---- ----- ------
system32 NT SERVICE\TrustedInstaller CREATOR OWNER Allow 268435456...
After get-acl
Steps to reproduce
PowerShell console messages are not displayed with correct order. This issue happens with a lot of cmdlets but some cmdlets(ex get-process/get-service) work well. For example, run the following script. You can see the messages shown with wrong order. I know 'Out-Default' is called internally from most of get-xxx cmdlets but it looks like it does't work in some cases. I think console messages should be displayed sequentially with correct order because 'Out-Default' is called internally. But actual behavior is not(Out-Default is called but the message is buffered and not displayed). So please check if this is a bug or by design with host message buffering.
Expected behavior
The output messages are displayed in powershell console/ISE with the following order.
Actual behavior
The powershell console/ISE shows the messages in wrong order like this. The output of get-acl is buffered and not displayed and message of Read-Host appears prior to output of get-acl.
Environment data
The text was updated successfully, but these errors were encountered: