Perforce for VS Code extension - causes "Activating Extensions ..." indefinitely

[amal-khailtash]

Describe the bug:

I used extensions bisect and that identified this extension causing "Activating Extensions..." indefinitely. Disabling this extension, makes other extensions work properly.

Expected behavior: My extensions do not activate properly!

To Reproduce: Using latest VSCode 1.95.3 causes this issue.

Versions & Details:

• Perforce extension: v4.16.1

• VSCode Version: 1.95.3 Commit: https://github.com/microsoft/vscode/commit/f1a4fb101478ce6ec82fe9627c43efbf9e98c813 Date: 2024-11-13T14:50:04.152Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Linux x64 4.18.0-553.22.1.el8_10.x86_64

• Perforce server details (if known):

• Are you using a multi-root workspace?: No

Additional context

Performing one-time registration of perforce commands
==============================
Workspace folders changed. Starting initialisation.

Workspaces were added
> file:///home/amal/root: Trying to initialise SCM Providers in this workspace.
	Note: the following overrides apply in this workspace:
		perforce.port: none	(will not override)
		perforce.user: none	(will not override)
		perforce.client: none	(will not override)
		perforce.dir: none	(will not override)
	Explicit overrides may prevent auto-detection of other perforce client workspaces
Looking for a client root using the workspace root directory
/home/amal/root: p4 'info'
> file:///home/amal/root: Found workspace using root directory
  * VS Code workspace root directory :
	Client name: akhailta_root
	Client root: /home/amal/root
	User name: akhailta
	Server address: atlp4s08.amd.com:1677
	Folder IS in or above client root
> file:///home/amal/root: Looking for perforce config files
/home/amal/root: p4 'set' '-q'
> file:///home/amal/root: Using pattern **/P4CONFIG

[mjcrouch]

Hi, is it only in this version? I.e. was it working ok in a previous version of vscode?

Based on the log it looks like it might be scanning for p4config files. Do you have a lot of files in the workspace? If you don't use p4config you could try disabling perforce.enableP4ConfigScanOnStartup

[amal-khailtash]

This seemed to work for VSCode 1.95.0. When I upgraded, it started to happen. I do have a P4CONFIG in the root of the workspace, not sure why it is not using that!

[amal-khailtash]

Added perforce.enableP4ConfigScanOnStartup = false, shows the Changelists without the initial scan, but my other extensions are still not working and I see "Activating Extensions..."