# 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: job000419
Status: open
Project: perforce-software-p4api-net
Severity: B
ReportedBy: norman_morse
ReportedDate: 2015/12/09 09:27:43
ModifiedBy: norman_morse
ModifiedDate: 2015/12/09 09:27:43
Description:
Exclude client data option is broken.
From customer in case 002112692
The flag for "exclude client data" seems to be wrong (or at least inconsistent with the others). See https://swarm.workshop.perforce.com/files/guest/perforce_software/p4api.net/p4api.net/Options.cs, line 8729:
this["Os"] = null;
I believe this should say
this["-Os"] = null;
The current state makes GetFileMetadataCmdFlags.ExcludeClientData unusable since it sends "Os" with the command (as opposed to "-Os") and Perforce interprets that as a filespec and complains that no file "Os" exists.
DevNotes:
Type: Bug