|Title||Whitespace lines in Bugzilla descriptions can break replicator|
|Assigned user||Nick Barnes|
|Description||The Perforce server does not preserve lines in job text fields which only contain whitespace. It replaces them with empty lines. If those lines have come from a Bugzilla longdesc record, this will then break the replicator (because the replicator will try to replicate the job back to Bugzilla, the empty line will show up as different to the whitespace-only line, and the "append-only" restriction will kick in. The job will be overwritten by the job but this will not fix the problem, so it will happen again on the next poll.|
|Analysis||Report this as a bug in Perforce. The replicator could work around this by replacing whitespace-only lines in Bugzilla longdesc records with empty lines as they are read from the Bugzilla database.|
This first showed up as job000364, which is a special case. The fix for that (changelist 14331) does not fix this.
Perforce logged this as an enhancement request .
GDR 2001-08-07: The Perforce part of this is Perforce job 6149.
|Evidence||Reading the code and running some test jobs.|
|Created by||Nick Barnes|
|Created on||2001-07-25 12:49:40|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:53:40|
|History||2001-07-25 NB Created.|
|14474||closed||2001-07-25 13:29:48||Nick Barnes||Non-empty blank lines must be cleared when reading from Bugzilla, or Perforce will do it for us and confuse the replicator.|