Setting or overriding the client doesn't work

[jmarkiewicz]

I am unable to use this plugin anymore. At best its been sporadic. At the moment it can't figure out the p4 client.

I have a p4.ini in the directory. Running commands from cmd.exe recognizes the values of p4 set.

Running p4 set manually from the terminal results in the following PS D:\Depot> p4 set P4CLIENT=MYCLIENT_RELEASE (config 'd:\Depot\p4.ini') P4CONFIG=p4.ini (set) (config 'd:\Depot\p4.ini' ) P4EDITOR=C:\Program Files (x86)\Notepad++\notepad++.exe (set) P4IGNORE=.p4ignore.txt (set) P4PORT=perforce:1666 (set) P4USER=josh.markiewicz (set) P4_perforce:1666_CHARSET=none (set)

Running the P4 info command from the plugin results in the following.

ERROR: "Client 'MYCLIENT_RELEASE' unknown - use 'client' command to create it.\r\n" "C:\Program Files\Perforce\p4.exe" -u josh.markiewicz -p perforce:1666 info User name: josh.markiewicz Client name: MYCLIENT_RELEASE Client host: MyMachine Client unknown. Current directory: d:\Depot
Peer address: xxxxxx Client address: xxxxxx Server address: server.net:1666 Server root: /p4/metadata/root Server date: 2020/02/07 09:41:04 -0500 EST Server uptime: 127:31:54 Server version: P4D/LINUX26X86_64/2019.1/1876401 (2019/10/30) ServerID: master Server services: standard Server license: License Server license-ip: ipaddress Case Handling: insensitive

[mjcrouch]

Hi @jmarkiewicz - I've forked the extension as there doesn't seem to be anyone active left on this project.

I published a change today to add additional logging to the perforce output when it tries to initialise everything.

I haven't changed any of the actual activation logic, so it probably won't fix your issue, but it might be easier to understand what's happening by looking at the perforce log output. (don't forget to disable / uninstall the slevesque version as they will conflict with each other)