Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Windows XP Pro SP3
Description
SCM polling is getting "Fatal Parse Error". See attached log. Here is error message:
FATAL: Parse error. Unable to find an item within a changeset. Please report this as a bug. Changesetdata = "
Changeset: 1501840
User: TLR\U0096898
Date: Dec 26, 2012 3:00:15 PM
Comment:
jQuery UI Upgrade
".
[8mha:AAAAWB+LCAAAAAAAAABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=[0mnull
FATAL: Aborted
[8mha:AAAAWB+LCAAAAAAAAABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=[0mDone. Took 6.6 sec
No changes
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | redsolo [ redsolo ] | jeffolson [ jeffolson ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Workflow | JNJira [ 147021 ] | JNJira + In-Review [ 192197 ] |
Dig a little digging on this....looks like the problem is that our developer used "------------" within his changeset comment. This causes the code at line 247 of DetailedHistoryCommand (in the ChangeSetStringReader.readChangeSet method) to think that a new changeset is starting. We can fix the comment for now to avoid the problem. Is there any way to make the ChangeSetStringReader parser smarter somehow?