checkheads: give up on processing locally unknown changeset
authorPierre-Yves David <pierre-yves.david@ens-lyon.org>
Wed, 29 Mar 2017 16:28:15 +0200
changeset 2246 fb4ef91f888e
parent 2245 a14e05e4bb20
child 2247 2320a7e3cbd7
checkheads: give up on processing locally unknown changeset There are too many issue with locally unknown changesets, we ignore them for now while we get the core feature of the detection working.
hgext3rd/evolve/checkheads.py
--- a/hgext3rd/evolve/checkheads.py	Tue Mar 21 23:44:30 2017 +0100
+++ b/hgext3rd/evolve/checkheads.py	Wed Mar 29 16:28:15 2017 +0200
@@ -193,6 +193,8 @@
     # XXX as above, There are several cases this code does not handle
     # XXX properly
     #
+    # * We "silently" skip processing on all changeset unknown locally
+    #
     # (1) if <nh> is public, it won't be affected by obsolete marker
     #     and a new is created
     #
@@ -205,9 +207,13 @@
     # In addition, this code is confused by prune as it only looks for
     # successors of the heads (none if pruned) leading to issue4354
     repo = pushop.repo
+    unfi = repo.unfiltered()
     newhs = set()
     discarded = set()
     for nh in candidate:
+        if nh not in unfi:
+            newhs.add(nh)
+            continue
         if nh in repo and repo[nh].phase() <= phases.public:
             newhs.add(nh)
         else: