# 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:	job000712

Status:	open

Project:	perforce-software-p4eclipse

Severity:	B

ReportedBy:	amo

ReportedDate:	2017/06/07 08:43:14

ModifiedBy:	perforce

ModifiedDate:	2019/02/19 10:51:37

OwnedBy:	adam_morriss

Description:
	"REFRESH" error on CTRL-C anywhere in Eclipse with P4Eclipse
	
	Some users report that the message: "occasionally there are messages thrown into the terminal of which Eclipse is running from", e.g.
	REFRESH:preExec >>> Selection= org.eclipse.jface.text.TextSelection@4ddf3b46
	is reported occasionally in the terminal from which Eclipse is running, and they occur when the user presses CTRL-C anywhere in Eclipse. They see this only when P4Eclipse is added to their Eclipse environment.
	
	They are using
	Eclipse Platform
	Version: Mars.2 (4.5.2)
	Build id: M20160212-1500
	P4Eclipse - Perforce Team Provider
	Version: 2016.1.1409747
	
	
	Potential reference to the warning on line 126/127 in here: 
	https://swarm.workshop.perforce.com/projects/perforce-software-p4eclipse/files/2015-1/src/3.7/plugins/com.perforce.team.ui/src/com/perforce/team/ui/PerforceUIPlugin.java

DevNotes:

Type:	Bug