Skip to content
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

VSCode Terminal drops output from AWS CLI #42847

Closed
jdalley opened this issue Feb 2, 2018 · 3 comments
Closed

VSCode Terminal drops output from AWS CLI #42847

jdalley opened this issue Feb 2, 2018 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues

Comments

@jdalley
Copy link

jdalley commented Feb 2, 2018

I had posted this as a question on Stack Overflow and unfortunately hadn't received any insight from it - so I was encouraged to drop this here as an issue.

Summary:
While running some AWS CLI commands recently via Powershell in the VSCode terminal, I noticed it completely drops/doesn't render all the output.

  • VSCode Version: 1.19.3
  • OS Version: Windows 10 Pro (Version 1709, Build 16299.214)
  • Powershell PSVersion: 5.1.16299.98

Steps to Reproduce:

  1. On a machine with AWS CLI set up, make a call that results in a moderate size (50+ lines) of output. In my case I used: aws elb describe-load-balancers.
  2. This command will show anywhere between 14 and 122 lines of output before returning (cut-off) to the prompt. Whereas if I take the same command and run it in a standalone instance of Powershell it will print all 971 lines.

Additional Information:

  • This happens on a fresh terminal window with no previous buffered lines.
  • I'm using the same powershell .exe configured in VSCode's terminal as I ran standalone:
    "powershell.powerShellExePath": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe", "terminal.integrated.shell.windows":"C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
  • This doesn't seem to be caused by the terminal.integrated.scrollback setting - it's set quite high, and like I said it can get cut off at a low number of printed lines.

Does this issue occur when all extensions are disabled?: Yes

@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Feb 2, 2018
@Tyriar
Copy link
Member

Tyriar commented Feb 21, 2018

@jdalley I notice you are using the powershell extension, does this happen when running through on of the extension's integrated consoles?

@Tyriar Tyriar added the info-needed Issue requires more information from poster label Feb 21, 2018
@jdalley
Copy link
Author

jdalley commented Feb 21, 2018

This does happen through the "PowerShell Integrated Console" as well as the default Integrated Terminal - both will cut off output.

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues and removed info-needed Issue requires more information from poster labels Mar 7, 2018
@Tyriar
Copy link
Member

Tyriar commented Jun 21, 2018

This is likely related to winpty, tracking in #45693

@Tyriar Tyriar closed this as completed Jun 21, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 21, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

2 participants