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

Off by one rendering of the current text in the prompt #8711

Closed
KirillOsenkov opened this issue Jan 5, 2021 · 2 comments
Closed

Off by one rendering of the current text in the prompt #8711

KirillOsenkov opened this issue Jan 5, 2021 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@KirillOsenkov
Copy link
Member

Environment

Windows build number: Version 10.0.19042.685
Windows Terminal version (if applicable): 1.4.3243.0

Steps to reproduce

I wasn't able to reproduce at will but I've seen this a few times

Expected behavior

Things work as expected

Actual behavior

Current prompt text is rendered one line below where it's supposed to be
TerminalOffByOne

I have no idea how to investigate or reproduce this, but I'm filing this to raise awareness that the issue exists, and will probably be very difficult to hunt down.

If you have any tips on the steps I could do to debug this next time I see this, I'd be happy to try them out.

@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 Jan 5, 2021
@zadjii-msft
Copy link
Member

Shockingly, I think we've seen this before. #6546 is tracking just about the same bug, and some other related ones are in #5800. I get something like this every so often, but it's terribly hard to track down.

If you had consistent repro steps, that would probably be the most useful thing. Unfortunately, this kind of bug is really hard to debug once it's already happened - it's usually best to get a trace of it starting to happen. However, without consistent repro steps, it's incredibly hard to get such a trace 😕

I'm gonna close this as a /dupe of #6546, but please hop on that thread if you do find a consistent repro!

@ghost
Copy link

ghost commented Jan 6, 2021

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 Jan 6, 2021
@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 labels Jan 6, 2021
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

2 participants