| Title | New Bugzilla bugs may cause conflict email |
| Status | closed |
| Priority | critical |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If a Bugzilla bug is created or changed in the same second as the start of a replicator poll, it may be replicated on two consecutive polls. This will cause a conflict email to be sent on the second poll. |
| Analysis | This is because the replicator is also then trying to replicate the new job back to Bugzilla because it can't tell that the job change was made by itself; see job000016. Need to think hard about the SQL logic in all_bugs_since(). Maybe add more SQL to exclude exactly this case. Added SQL to exclude changes in the same second as the start of the current replication. These changes will be picked up by the next replication. Note that this introduces the more serious problem job000339, but that will be very much more rare. |
| How found | customer |
| Evidence | <http://info.ravenbrook.com/mail/2001/02/28/00-41-34/0.txt> |
| Observed in | 0.5.1 |
| Introduced in | 0.5.0 |
| Created by | Nick Barnes |
| Created on | 2001-02-28 14:32:47 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:26:56 |
| History | 2001-02-28 NB Created. 2001-03-01 NB Added note concerning fix. 2001-06-27 NB Added link to job000339. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 9237 | closed | 2001-03-01 11:32:51 | Nick Barnes | Fixes for job000235 and job000236; bugzilla timings and database growth. |