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

Extra whitespace when running jest tests in a PowerShell window. #7605

Closed
Butters646 opened this issue Sep 11, 2020 · 6 comments
Closed

Extra whitespace when running jest tests in a PowerShell window. #7605

Butters646 opened this issue Sep 11, 2020 · 6 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Butters646
Copy link

I don't know if this is specific to jest, that is just how I observed this behavior. I get large "chunks" of whitespace in my terminal session when I run my tests. This doesn't happen when I use PowerShell directly or when I use the command prompt in Windows Terminal, so it looks like it is an issue with the PowerShell window in Window Terminal.

I have attached screenshots of the issue. This is just one example of the extra space. Huge chunks of blank lines appear throughout the run in the PowerShell window.

cmd prompt Window in Windows Terminal
PowerShell stand alone Window
PowerShell Window in Windows Terminal

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 11, 2020
@DHowett
Copy link
Member

DHowett commented Sep 16, 2020

This is very unexpected. When you run it in a normal powershell window, does the size of the window change?

@DHowett DHowett added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Sep 16, 2020
@Butters646
Copy link
Author

@DHowett It doesn't appear to. I see no observable window size changes.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Sep 16, 2020
@zadjii-msft
Copy link
Member

@Butters646 could you share your powershell profile? I've got a theory that some customization in there is what's tripping the Terminal up

@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Sep 29, 2020
@Butters646
Copy link
Author

Microsoft.PowerShell_profile.zip

Sure. Attached.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Sep 29, 2020
@DHowett
Copy link
Member

DHowett commented Oct 1, 2020

image

that'll do it!

/dup #5094

alternatively, don't force the screen or buffer size in the file that powershell runs for every new session (including when it's spawned by other poorly-behaved tools sometimes!)

@ghost
Copy link

ghost commented Oct 1, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 1, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements Needs-Attention The core contributors need to come back around and look at this ASAP. labels Oct 1, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants