# The form data below was edited by perforce # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # 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. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000741 Status: open Project: perforce-software-p4convert Severity: A ReportedBy: norman_morse ReportedDate: 2018/12/10 11:13:24 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:40 OwnedBy: norman_morse Description: Labels with spaces cause a crash in the converter. From case 00369890, dump files are on warp:/warp/cases/00369890 Conversion has no problems until we enable the "exclude.map", which throws this exception: 03 Dez 2018 11:31:25,356 ERROR com.perforce.common.process.ProcessChange ... Caught exception on exit java.lang.ArrayIndexOutOfBoundsException: 2 at com.perforce.p4java.impl.generic.core.MapEntry.parseViewMappingString(MapEntry.java:279) at com.perforce.p4java.impl.generic.core.MapEntry.<init>(MapEntry.java:74) at com.perforce.p4java.impl.generic.core.Label$LabelMapping.<init>(Label.java:117) at com.perforce.common.label.LabelImport.buildViewMap(LabelImport.java:183) at com.perforce.common.label.LabelImport.submit(LabelImport.java:170) at com.perforce.common.process.ProcessLabel.submit(ProcessLabel.java:143) at com.perforce.common.process.ProcessChange.submit(ProcessChange.java:195) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:187) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:59) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:21) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 03 Dez 2018 11:31:25,366 INFO com.perforce.common.process.ProcessChange ... Caught EXIT shutting down ... cat exclude.map # exclude Subversion tags: ^tags/.* I am able to reproduce this, in the debugger the crash happens in com.perforce.p4java.impl.generic.core.MapEntry.parseViewMappingString(MapEntry.java:279) which seems to get confused by spaces in the client entry. DevNotes: Type: Bug