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

Terminal Running Previous codes and having bugs #3808

Closed
salah443 opened this issue Jan 7, 2025 · 1 comment
Closed

Terminal Running Previous codes and having bugs #3808

salah443 opened this issue Jan 7, 2025 · 1 comment
Assignees
Labels
triage-needed Issues needing to be assigned to the prospective feature owner

Comments

@salah443
Copy link

salah443 commented Jan 7, 2025

Type: Bug

dear microsoft team
i will like to report a continuous error of my vs code terminal, or, the app itself. iever since i downloaded it the second time, the terminal has always been misbehaving. it always runs codes that i previously ran, and, doesn't run modified and updated codes. if it runs something and brings out an output, if i change the code to output a different thing, it still brings the output of my previous code. same to errors. if an error pops, and then, i clear the error completely, it still bringd out that error. i don'tknow why this happens, so, i hope it is fixed, so i can finally complete ,y project.
yours sincerely
hamza obabu

VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info
Item Value
CPUs Intel(R) Pentium(R) CPU 4417U @ 2.30GHz (4 x 2304)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 3.92GB (0.30GB free)
Process Argv --crash-reporter-id 20c57153-7155-4b86-9db2-8ea67547aadc
Screen Reader no
VM 0%
Extensions (12)
Extension Author (truncated) Version
codeium Cod 1.30.18
csdn-codegpt CSD 1.1.2
gitlens eam 16.1.1
copilot Git 1.254.0
copilot-chat Git 0.23.2
path-autocomplete ion 1.25.0
vscode-peacock joh 4.2.2
debugpy ms- 2024.14.0
python ms- 2024.22.1
vscode-pylance ms- 2024.12.1
autoimport ste 1.5.4
errorlens use 3.22.0
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31179979
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyonecf:30548226
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

@github-actions github-actions bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Jan 7, 2025
@joyceerhl joyceerhl assigned Tyriar and unassigned joyceerhl Jan 7, 2025
@Tyriar
Copy link
Member

Tyriar commented Jan 7, 2025

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to our code. As such, I will go ahead and close it. Please try to reproduce in Windows Terminal and report to microsoft/terminal with repro steps.

If you cannot reproduce in Windows Terminal, chances are it's fixed in a later version of Windows. You can read more about how we consume conpty here. Additionally, soon we plan on shipping conpty v2 with VS Code which should bring our behavior in line with Windows Terminal. Thanks for understanding.

/label upstream terminal-conpty windows

@Tyriar Tyriar closed this as completed Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-needed Issues needing to be assigned to the prospective feature owner
Projects
None yet
Development

No branches or pull requests

3 participants