# The form data below was edited by norman_morse
# Perforce Workshop Jobs
#
# Job: The job name. 'new' generates a sequenced job number.
# Status: Job status; [open/closed/suspended]. Required
# Project: The project this job is for. Required.
# Severity: [A/B/C] (A is highest) Required.
# ReportedBy The user who created the job. Can be changed.
# ReportedDate: The date the job was created. Automatic.
# ModifiedBy: The user who last modified this job. Automatic.
# ModifiedDate: The date this job was last modified. Automatic.
# OwnedBy: The owner, responsible for doing the job. Optional.
# Description: Description of the job. Required.
# DevNotes: Developer's comments. Optional.
# Type: Type of job; [Bug/Feature]. Required.
Job: job000530
Status: open
Project: perforce-software-p4connect
Severity: B
ReportedBy: norman_morse
ReportedDate: 2016/06/02 10:34:16
ModifiedBy: norman_morse
ModifiedDate: 2016/06/02 10:34:16
Description:
Occasional failures to check out files.
When using P4Connect there are occasions when it will fail to checkout a file. Sometimes the following error will appear in a dialog box
“file.cs isn't in the depot and cannot be checked out, the file will be marked for add instead”
Other times it fails silently with the following in the log file
2016-06-01 17:03:11,850 DEBUG P4Connect.Engine+Collector.Add - add: file: Assets/Scripts/Common/Client/Components/UI/ViewLoader.cs mfile: null
The latter was observed by Norman Morse on his visit to our studio and was recreated by modifying a file with the Unity project in Visual Studio and then going back to Unity and waiting for it to respond to the changed file.
from internal case 00240704
DevNotes:
Type: Bug