[p4dti-discussion] P4DTI - Job bugXXXX overwritten by issue XXXX

[Brent Browning]

Same here, but too late as bugs have already been filed with Unicode
characters.

Bugzilla doesn't allow editing of comments, so how can I fix the
problem?  Or are you suggesting I edit the affected Perforce jobs?

- Brent 

-----Original Message-----
From: p4dti-discussion-bounces at ravenbrook.com
[mailto:p4dti-discussion-bounces at ravenbrook.com] On Behalf Of
n.herring at atlantiscyberspace.com
Sent: Friday, April 11, 2008 4:37 PM
To: p4dti-discussion at ravenbrook.com
Subject: Re: [p4dti-discussion] P4DTI - Job bugXXXX overwritten by issue
XXXX

I banned my developers from copy/pasting from Word or anything that
might add silly characters into the description. Not a fix, but just
letting you know that you are not the only one having this problem. You
will continue to get the spam until you go back and fix the changelist
descriptions with those characters in there.

-----Original Message-----
From: p4dti-discussion-bounces at ravenbrook.com
[mailto:p4dti-discussion-bounces at ravenbrook.com] On Behalf Of Brent
Browning
Sent: Friday, April 11, 2008 11:31 AM
To: p4dti-discussion at ravenbrook.com
Subject: [p4dti-discussion] P4DTI - Job bugXXXX overwritten by issue
XXXX

We have been happily using P4DTI for years now.  Recently we have been
hit by the UnicodeDecodeError problem where Bugzilla users enter
non-ASCII characters in their bug reports and P4DTI fails to poll with:

(P4DTI-891X)  Error (exceptions.UnicodeDecodeError): 'ascii' codec can't
decode byte 0x91 in position 119: ordinal not in range(128)

There must be a fix that allows Unicode characters to be present in
Perforce or strips out the non ASCII characters and ignores them in the
comparison.  This might be related to the real problem or not.

The real problem we have today is that P4DTI has gone runaway.  That is,
we are getting a TON of messages like this:

(P4DTI-8410)  Defect tracker issue '5239' and Perforce job 'bug5239'
have both changed since the last time the replicator polled the
databases.  The replicator's conflict resolution policy decided to
overwrite the job with the issue.

I have seen 160 in the past hour and had to shutdown P4DTI.  I checked
the bugs and jobs in question and no one is making changes on either
side.

What gives?

- Brent


_______________________________________________
P4DTI-discussion mailing list
P4DTI-discussion at ravenbrook.com
http://mailman.ravenbrook.com/mailman/listinfo/p4dti-discussion

_______________________________________________
P4DTI-discussion mailing list
P4DTI-discussion at ravenbrook.com
http://mailman.ravenbrook.com/mailman/listinfo/p4dti-discussion