CODEWITHSUNDEEP
command-lineperforce
Gabriel Lacey
Gabriel Lacey

Reputation: 3

Perforce CLI reconcile adds 'ghost' files to my working directory

Have a perplexing bug when I try to reconcile work through the CLI for perforce in that I get a large amount of files detected and added to the changelist whenever I run the command.

This happens regardless of where my current working directory is but the files always come from there, if my working directory is outside the project's root I get a 'Path {path} is not under client's root' error and they are not added, however if my working directory is under the project root they are detected and added as missing files.

I've tried numerous different combinations of the reconcile command, explicitly stating the port, user, client etc., setting up P4Config, using relative and absolute paths, changing the working directory - but I always get these ghost files.

Has anyone come across this before? Could this be a bug with P4 itself?

Edit: I finally fixed this by reinstalling P4V so I'm assuming this was some bug either my install of perforce or any local config files that would have been reset upon reinstall. For reference this is the page that finally fixed it https://community.perforce.com/s/article/15324

Upvotes: 0

Views: 221

Answers (2)

Samwise
Samwise

Reputation: 71454

This is the result of the following bug:

https://www.perforce.com/perforce/doc.current/user/relnotes.txt

Bugs fixed in 2020.1 Patch 1 (2020.1/1991450)

    ...

    #1964794 (Job #102470) *
        'p4 reconcile'/'p4 status' might report about invalid filenames
        of the form '//depot/0' or '//depot/100', etc.  This is fixed.

Since this was fixed in a 2020.1 patch, it can be inferred that it only affects specific 2020.1 builds (i.e. those before the patch).

To fix it, make sure you're on a client version (p4 or P4V; this is not a server-side bug) whose changelist number is higher than 1964794. No special reinstallation procedure is needed; just download the latest binary/installer from Perforce's website.

Upvotes: 0

Gabriel Lacey
Gabriel Lacey

Reputation: 3

Force a reinstall of P4V to fix this, details can be found here: https://community.perforce.com/s/article/15324

Or if that page is taken down for any reason:

SOLUTION Forcing a reinstall using the Windows msiexec installer utility with Windows msi installer file extracted from the p4vinst64.exe file can often successfully complete a full reinstall where running the P4V exe installer such as "p4vinst64.exe" fails

If not already downloaded, obtain the appropiate Windows installer for P4V (for example "p4vinst64.exe" for 64 bit Windows platforms). Currently these can be downloaded from https://www.perforce.com/downloads/helix-visual-client-p4v

Extract the msi from p4vinst64.exe; for example to extract it to "c:\p4v", open a Windows a cmd prompt and change directory to the location where p4vinst64.exe .is located and run the following command:

p4vinst64.exe /s /b"c:\p4v" /v"/qn"

Now from c:\p4v, run the following command to force a full reinstall: msiexec /i "p4vinst64.msi" /qn REINSTALL=ALL REINSTALLMODE=vamus /L*v log.txt

Upvotes: 0

Related Questions