microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.53k stars 29.4k forks source link

Two source control panes (One works fine, but the other shows nothing) #106564

Closed Biswas-N closed 4 years ago

Biswas-N commented 4 years ago

Issue Type: Bug

  1. Source Control pane appears twice
  2. One shows the expected file changes, but the other shows nothing

VSCODE_ISSUE

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

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (4 x 2592)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|7.89GB (2.51GB free)| |Process Argv|--crash-reporter-id ed8ac75a-5bab-4432-89df-bc7a172b1f38| |Screen Reader|no| |VM|0%|
Extensions (22) Extension|Author (truncated)|Version ---|---|--- vscode-eslint|dba|2.1.8 gitlens|eam|10.2.2 vsc-material-theme|Equ|33.0.0 vsc-material-theme-icons|equ|1.2.0 prettier-vscode|esb|5.6.0 go|gol|0.16.2 vscode-nuget-package-manager|jmr|1.1.6 vscode-styled-components|jpo|0.0.31 sftp|lix|1.12.9 rainbow-csv|mec|1.7.1 vscode-language-babel|mgm|0.0.29 csharp|ms-|1.23.2 python|ms-|2020.8.108011 remote-wsl|ms-|0.44.5 vsliveshare|ms-|1.0.2740 vsliveshare-audio|ms-|0.1.85 vsliveshare-pack|ms-|0.4.0 LiveServer|rit|5.6.1 mdx|sil|0.1.0 vscodeintellicode|Vis|1.2.10 vim|vsc|1.16.0 gitmoji-vscode|Vtr|0.2.2 (1 theme extensions excluded)
gjsjohnmurray commented 4 years ago

Are you certain that all extensions were disabled when you took that screenshot? Your status ba contains items that I don't recognise.

Biswas-N commented 4 years ago

Even after disabling all extensions, I am seeing two source control panes.

DisabledExtensions

sbatten commented 4 years ago

@Biswas-N can you right click next to the "Source Control" text in the empty pane and share the context menu that is shown? Same with right-clicking the icon?

Ttou commented 4 years ago

same issue, the first one can't use

WX20200916-160437

Biswas-N commented 4 years ago

@sbatten with the latest update of VS Code (1.49.2 on Windows), this bug seems to be fixed.

jdforsythe commented 4 years ago

I had the same issue (started with 1.49.1, I believe, as it's only been happening since last week), and upon upgrading to the newest update (1.49.2), the second Source Control tab also disappeared. The problem is, the one that disappeared was the only one that worked.

When there were two tabs, I noticed that when I right-clicked in the tab bar, there were two entries for Source Control - one with the keyboard shortcut listed (that's the one that had nothing inside it) and a duplicate (the one that actually listed the files).

Now after the update, the sole remaining Source Control tab has no files inside of it. I can right-click in the empty pane and turn on the "Source Control Repositories" option, which shows a single entry for the repository, but does not list any changed files. Now that I've turned on "Source Control Repositories", it is grayed out and I can no longer turn it off.

I did notice a new Source Control pane in the Explorer tab, which does work exactly as the old Source Control tab did, however I prefer using it in it's own tab.

sbatten commented 4 years ago

@jdforsythe that is helpful. I'm not sure what the steps taken were to get you into this state, either bug in code or UX was unclear; however, you should be able to get into your desired state by right-clicking the Source Control view in Explorer and clicking Reset Location.

Let me know if this works for you.

jdforsythe commented 4 years ago

@sbatten This did return the functionality to the Source Control tab. Thank you.

sbatten commented 4 years ago

thanks @jdforsythe, i will close this issue as it seems the duplicate icon issue is resolved and hopefully our discussion will provide support for anyone seeing their view moved without knowing how to return it home