# 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: job000286
Status: open
Project: perforce-software-p4api-net
Severity: A
ReportedBy: rhummer
ReportedDate: 2015/05/26 15:18:48
ModifiedBy: perforce
ModifiedDate: 2019/02/19 10:51:16
OwnedBy: rhummer
Description:
Issues with GetConfig.
We are seeing various issues when either trying to use Connection.GetP4EnvironmentVar, or when P4Server attempts to call P4Server.GetConfig() when a cwd is specified when connecting to the server.
I am either seeing a NullPtr exception, or an AccessViolation exception.
The null ptr exception looks like this:
at Perforce.P4.Connection.Connect(Options options) in c:\tmp\49030141\P4.NET\r14.2\p4api.net\p4api.net\Connection.cs:line 393
My example is pretty simple:
repo = new Perforce.P4.Repository(new Perforce.P4.Server(new Perforce.P4.ServerAddress(string.Empty)));
var options = new Perforce.P4.Options();
options.Add("ProgramName", "P4Test");
options.Add("cwd", System.Environment.CurrentDirectory);
if (repo.Connection.Connect(options))
{
var config = repo.Connection.GetP4EnvironmentVar("P4CONFIG");
Console.WriteLine("P4CONFIG={0}", config);
}
This is using the 64bit zip of the compiled libraries, of the latest release 2014.2. I am also seeing it from locally compiled source, but verified I am seeing it with the prebuilt libraries provided.
DevNotes:
Type: Bug