You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
No files are displayed in the SCM tab until I do a manual sync from the extension. I do not know if this is a purposeful extension API change by MS that requires an update or a regression in vscode.
Expected behavior:
Tab should populate with my workspace upon opening, like it did in vscode 1.75.2.
To Reproduce:
Open workspace with p4client configured, go to SCM tab and see that it is empty.
Versions & Details:
Perforce extension: 4.15.5
VSCode version: 1.76.0
Operating System: Ubuntu Linux 22.10
Perforce server details (if known):
Are you using a multi-root workspace?: No
Additional context
The text was updated successfully, but these errors were encountered:
thanks for reporting! I just had a quick look and can reproduce - it looks like a bug in the vscode API where a previously released API has been marked as experimental. It causes an exception leading to the initial sync being interrupted (and will also break the quick diffs in the editor). I've reported @ microsoft/vscode#175888
Describe the bug:
No files are displayed in the SCM tab until I do a manual sync from the extension. I do not know if this is a purposeful extension API change by MS that requires an update or a regression in vscode.
Expected behavior:
Tab should populate with my workspace upon opening, like it did in vscode 1.75.2.
To Reproduce:
Open workspace with p4client configured, go to SCM tab and see that it is empty.
Versions & Details:
Additional context
The text was updated successfully, but these errors were encountered: