Open
Bug 1127512
Opened 10 years ago
Updated 6 years ago
pushlog replication doesn't behave well with missing changesets
Categories
(Developer Services :: Mercurial: Pushlog, defect)
Developer Services
Mercurial: Pushlog
Tracking
(Not tracked)
NEW
People
(Reporter: gps, Unassigned)
References
Details
Somehow mozilla-beta replication got into a weird state where mirrors were missing some changesets. However, the pushlog data transferred down just fine.
The json-pushes was advertising changesets that didn't exist in the local repo. However, pushloghtml or json-pushes?full=1 were failing due to the repo raising a LookupRepoError when the pushlog was trying to access the changeset on the underlying repo, which didn't exist.
I'm not sure the best way to tackle this. Refusing to pull pushlog entries for which there are no local changesets might be doable. Another would be to filter missing changesets from the pushlog output. Another would be to annotate missing changesets in the pushlog output. No easy solution :/
Reporter | ||
Comment 1•7 years ago
|
||
See also bug 1456998.
You need to log in
before you can comment on or make changes to this bug.
Description
•