Bug Fixes

#1042783 (Bug #78427) * 'p4 -P <ticket> sync --parallel' will no longer give authentication errors for the file transfer sub-processes.

#1039837 (Bugs #73075, #74961) ** The revision specifier @client was not working properly for clients bound to a build-server.

#1039277 (Bug #78383) ** A 'p4 describe' command which accesses a remote promoted shelf now properly reports any communications-related error conditions which occur when retrieving the remote shelf.

#1038837 (Bug #78164) ** In a distributed environment, the change-failed trigger now runs on the commit server rather than on the edge server.

#1037755 (Bug #76982) * If a 'p4 sync --parallel' child process encounters an error writing files to the local machine, the parent 'p4 sync' command now returns a non-zero exit status to the operating system.

#1036625 (Bug #77433) ** In a distributed configuration, 'p4 unshelve' no longer takes the global exclusive file lock for a file of type +l which is unshelved for add.

#1036397 (Bugs #75463,#77069) ** Edge Server commands which access promoted shelves created on other Edge Servers could fail due to corrupted network buffers.

#1035781 (Bug #78256) ** A replica running 2014.2 or later which is connected to an earlier master server no longer displays 'Unknown command' when the 'p4 pull -lj' command is run.

#1032010 (Bugs #74056,#71961) ** 'p4 sync --parallel' would fail to expand RCS keywords properly. And 'p4 sync --parallel' would fail with the message "Can't clobber writable file" if the file was changed from filetype binary+w to filetype binary (or text+w to text) by the revision being sync'd.

#1031192 (Bug #76013) ** 'p4d -xx db.working db.have' could create spurious delete records for db.working if a file opened for move or delete is subsequently moved and submitted by another client and the opened file is then synced to the head revision.

#1030571,#1030398 (Bug #77559) ** A build-server replica would incorrectly process the View: field for labels, causing the wrong set of revisions to be specified by the label.

#1028560 (Bug #77558) ** A replica with lbr.replication=cache was not able to access labels using the autoreload option.

#1027695 (Bug #77595) ** 'p4 export -f' now formats the domain type column correctly for unloaded clients, unloaded labels, and unloaded task streams.

#1026707 (Bug #77504) ** * 'p4 -Zproxyload sync --parallel=...' now correctly updates the proxy's archive cache without sending files to the client.

#1026534 (Bug #77280) ** If a change submitted via an Edge Server was rejected by a change-submit or change-content trigger on the Commit Server, the change's files were modified to read-only mode on the client machine rather than being left in writable mode.

#1026233 (Bug #77435) ** A 'p4 integ' or 'p4 unshelve' command on an Edge Server which failed to open a +l file due to a client-side file transfer error would leave an orphaned lock record in db.excl.

#1023372 (Bug #77818) ** Promoting a shelf to a commit server from an edge server might not transfer all file content. This issue could only be reproduced with end-to-end server SSL and a broker placed between the commit and the edge server. It is likely that under other timing conditions/latency this problem could also occur without this specific configuration.

#1010415 (Bug #77471) ** The 'reload -p' command, used to migrate a workspace from one Edge Server to another, or between an Edge Server and the Commit Server, failed in certain specialized licensing scenarios.

#1008489 (Bug #77390) ** In a distributed installation, a pending change can be viewed on a server other than the server where the change was created. In such a situation, the pending change will not display a list of open files (the open files are shown only on the owning server). The 'change -d' command would incorrectly allow the pending change to be deleted if the command was issued on a server other than the owning server; this behavior is fixed and the command is now rejected with an appropriate error message.

#1004762 (Bug #77358) ** Fixed a crash that could occur when unshelving moved files to a different branch.