Skip to content

Terminal stops displaying Variable output #4114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 of 6 tasks
Fimlore opened this issue Aug 8, 2022 · 5 comments
Closed
5 of 6 tasks

Terminal stops displaying Variable output #4114

Fimlore opened this issue Aug 8, 2022 · 5 comments
Labels
Bug: PowerShell 5.1 Bugs when using PowerShell 5.1. Issue-Bug A bug to squash. Resolution-Duplicate Will close automatically.

Comments

@Fimlore
Copy link

Fimlore commented Aug 8, 2022

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all open and closed issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.

Summary

During usage of the Powershell Extension, it all of a sudden stops displaying data contained in Variables, like in the example below:
Powershell_Terminal_Exampla1

All of a sudden, it will completly stop echoing data and I have to force it with Write-Host, or Output-GridView
Powershell_Terminal_Exampla2

As you can see in the screenshot above, not a single variable outputs any data.

Powershell_Terminal_Exampla3

I dont feel like Im doing anything weird, I have scripts open that I work on, and as soon as I kill the Terminal, it will start working again --- but then I will loose the variables I was working with, and also all connections I have with services like MS Teams and Azure.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.22000.653
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22000.653
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.70.0
da76f93349a72022ca4670c1b84860304616aaa2
x64

Extension Version

code --list-extensions --showversions | Select-String powershell

ms-vscode.powershell

Steps to Reproduce

Have script open, get input stored into variable (I think, save the script) - variables no longer output.

Visuals

No response

Logs

No response

@Fimlore Fimlore added the Issue-Bug A bug to squash. label Aug 8, 2022
@ghost ghost added the Needs: Triage Maintainer attention needed! label Aug 8, 2022
@Fimlore
Copy link
Author

Fimlore commented Aug 8, 2022

It seems the issue does not occur in Powershell Core 7.1.2

@andyleejordan andyleejordan added the Bug: PowerShell 5.1 Bugs when using PowerShell 5.1. label Aug 8, 2022
@SydneyhSmith
Copy link
Collaborator

Thanks this seems related to #3991
@Fimlore could you please provide logs when this happens

@SydneyhSmith SydneyhSmith added Needs: Repro Info 🤔 and removed Needs: Triage Maintainer attention needed! labels Aug 11, 2022
@ghost
Copy link

ghost commented Aug 19, 2022

This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information!

@ghost ghost closed this as completed Aug 19, 2022
@andyleejordan andyleejordan added Resolution-Duplicate Will close automatically. and removed Needs: Repro Info 🤔 labels Feb 14, 2023
@andyleejordan
Copy link
Member

@Fimlore do you know if you have Start-Transcript somewhere before all this happens?

@ghost
Copy link

ghost commented May 5, 2023

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug: PowerShell 5.1 Bugs when using PowerShell 5.1. Issue-Bug A bug to squash. Resolution-Duplicate Will close automatically.
Projects
None yet
Development

No branches or pull requests

3 participants