http://hg.intevation.org/mercurial/file/2.5.2/mercurial/changelog.py#l204

Do you have the Changeset Evolution extension enabled? That code shouldn't kick in unless you do.

Something else to check: inside the .hg/store directory, do you have a file called obsstore?

The only enabled extension I have in TortoiseHG Settings / mercurial.ini is "rebase".

There is no "obsstore" file inside .hg\store directory.

*** Bug 3864 has been marked as a duplicate of this bug. ***

My guess:

changeset:   18395:904b7109938e
user:        Pierre-Yves David <pierre-yves.david@logilab.fr>
date:        Wed Jan 16 00:09:26 2013 +0100
summary:     destroyed: drop complex branchcache rebuilt logic

I've seen this happen at Facebook, too.

Probably related to http://bz.selenic.com/show_bug.cgi?id=3827 (fixed recently)

(In reply to comment #6)

Pierre-Yves, does that mean that you think this bug is also likely to have been fixed by that commit?

It might be fixed, but I'm not sure. Can Jan Rysavy details the command used for rebasing

Did you use --source or --base ?

U used following command: hg rebase --source 2490

I found this problem with TortoiseHG and originally reported it there:
https://bitbucket.org/tortoisehg/thg/issue/2483/freezed-in-the-rebase-dialog-box

thanks for the quick answer. Do you still have the repo handy. What is the phase of this 2488 changesets ?

Created attachment 1722 [details]
Graph with Phase column visilbe

See attached screenshot, does it help?
Yes, I have 7-Zip archive of this repo state.

What state is recorded in your archive? Does it allows to reproduce the issue ?

Yes, I can reproduce this problem.

Marvelous. Can you upload the archive somewhere and provide a minimal script to reproduce the issue ?

Unfortunately it is not possible. It is closed source commercial software, I'm sorry. Please let me know if I can do any tests, it is not a problem.

1) Can you check the rebase with the latest mercurila release (2.5.4)

2) Can you run the rebase with --debugger goes up withing the branchmap.update method (type "up" twice) then show up the content of `repo.filtername` and `repo.changelog.filteredrevs`

rebase --source 2490
saved backup bundle to X:\Test\ProtechCD\.hg\strip-backup\aa75bfb36958-backup.hg

** unknown exception encountered, please report by visiting
** http://mercurial.selenic.com/wiki/BugTracker
** Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)]
** Mercurial Distributed SCM (version 2.5.4)
** Extensions loaded: rebase
Traceback (most recent call last):
  File "hg", line 38, in <module>
  File "mercurial\dispatch.pyc", line 28, in run
  File "mercurial\dispatch.pyc", line 65, in dispatch
  File "mercurial\dispatch.pyc", line 88, in _runcatch
  File "mercurial\dispatch.pyc", line 743, in _dispatch
  File "mercurial\dispatch.pyc", line 514, in runcommand
  File "mercurial\dispatch.pyc", line 833, in _runcommand
  File "mercurial\dispatch.pyc", line 804, in checkargs
  File "mercurial\dispatch.pyc", line 740, in <lambda>
  File "mercurial\util.pyc", line 475, in check
  File "hgext\rebase.pyc", line 328, in rebase
  File "hgext\rebase.pyc", line 739, in clearrebased
  File "mercurial\repair.pyc", line 183, in strip
  File "mercurial\localrepo.pyc", line 58, in wrapper
  File "mercurial\localrepo.pyc", line 1425, in destroyed
  File "mercurial\branchmap.pyc", line 75, in updatecache
  File "mercurial\localrepo.pyc", line 634, in branchmap
  File "mercurial\branchmap.pyc", line 80, in updatecache
  File "mercurial\branchmap.pyc", line 192, in update
  File "mercurial\ancestor.pyc", line 230, in __iter__
  File "mercurial\changelog.pyc", line 204, in parentrevs
IndexError: 2488

Regarding your second question: I don't know Python nor Python debugger, I will need more detailed guidance here. I did:

X:\Test\ProtechCD>"C:\Program Files\Mercurial\hg.exe" rebase --source 2490 --deb
ugger
entering debugger - type c to continue starting hg or h for help
> x:\test\protechcd\mercurial\dispatch.pyc(87)_runcatch()
(Pdb) up
> x:\test\protechcd\mercurial\dispatch.pyc(65)dispatch()
(Pdb) up
> x:\test\protechcd\mercurial\dispatch.pyc(28)run()

What should I do next exactly?

The debugger wants the 'c' command to start running. It will drop you back to a prompt when something breaks. At that point, you can use 'u' to go up to the desired stack frame and 'p somevar' to print a variable.



It also might be worth trying to bisect the problem (see hg help bisect). Grab a copy of Hackable Mercurial for Windows here:

http://mercurial.selenic.com/wiki/HackableMercurial

..that will make it easy to test a sequence of changes.

Thank you! Requested values:

X:\Test\ProtechCD>"C:\Program Files\Mercurial\hg.exe" rebase --source 2490 --deb
ugger
entering debugger - type c to continue starting hg or h for help
> x:\test\protechcd\mercurial\dispatch.pyc(87)_runcatch()
(Pdb) c
saved backup bundle to X:\Test\ProtechCD\.hg\strip-backup\aa75bfb36958-backup.hg

Traceback (most recent call last):
  File "mercurial\dispatch.pyc", line 87, in _runcatch
  File "mercurial\dispatch.pyc", line 743, in _dispatch
  File "mercurial\dispatch.pyc", line 514, in runcommand
  File "mercurial\dispatch.pyc", line 833, in _runcommand
  File "mercurial\dispatch.pyc", line 804, in checkargs
  File "mercurial\dispatch.pyc", line 740, in <lambda>
  File "mercurial\util.pyc", line 475, in check
  File "hgext\rebase.pyc", line 328, in rebase
  File "hgext\rebase.pyc", line 739, in clearrebased
  File "mercurial\repair.pyc", line 183, in strip
  File "mercurial\localrepo.pyc", line 58, in wrapper
  File "mercurial\localrepo.pyc", line 1425, in destroyed
  File "mercurial\branchmap.pyc", line 75, in updatecache
  File "mercurial\localrepo.pyc", line 634, in branchmap
  File "mercurial\branchmap.pyc", line 80, in updatecache
  File "mercurial\branchmap.pyc", line 192, in update
  File "mercurial\ancestor.pyc", line 230, in __iter__
  File "mercurial\changelog.pyc", line 204, in parentrevs
IndexError: 2488
> x:\test\protechcd\mercurial\changelog.pyc(204)parentrevs()
(Pdb) up
> x:\test\protechcd\mercurial\ancestor.pyc(230)__iter__()
(Pdb) up
> x:\test\protechcd\mercurial\branchmap.pyc(192)update()
(Pdb) p repo.filtername
'immutable'
(Pdb) p repo.changelog.filteredrevs
frozenset([2488, 2490, 2491, 2492])
(Pdb)

What do the following commands say?

p bheadrevs
p newheadrevs
p latest

This smells like a cache invalidation issue. It's still not fixed, as we've been hitting it occasionally at FB where we run tip of crew. Unfortunately I haven't been able to get a reproducible test case for this.

(Pdb) p bheadrevs
[392, 2487, 2489, 2495, 2500, 2501, 2502, 2503, 2504]
(Pdb) p newheadrevs
[2489, 2495, 2500, 2501, 2502, 2503, 2504]
(Pdb) p latest
2504

Maybe we can arrange a teamviewer session so you can debug this problem on my machine?

I've just hit the issue on mercurial repo. Let me describe what has happened, while I have terminal session open (sorry for i18ned messages):

I had two draft changeset bookmarked "zsh":

 % hg out

набор изм-й:   18903:35111d556de8
автор:         Nikolaj Sjujskij <sterkrig@myopera.com>
дата:          Mon Apr 08 16:51:38 2013 +0400
сводка:        zsh_completion: make use of `debuglabelcomplete` command

набор изм-й:   18904:bd30c1ae9357
закладка:      zsh
метка:         tip
автор:         Nikolaj Sjujskij <sterkrig@myopera.com>
дата:          Tue Apr 09 19:58:04 2013 +0400
сводка:        zsh_completion: make use of `debugpathcomplete` command

They seem to have been branched off 8c0a7eeda06d (on Fri, Apr 12 in case that matters for cache invalidation).

Today (on Apr 15) I pulled in changes from main with 35111d556de8 being accepted as 5df602551eea. Naturally, I decided to rebase not yet finished 'bd30c1ae9357':

 % hg rebase -s 18904
bundle saved to /home/sterkrig/dev/mercurial/.hg/strip-backup/bd30c1ae9357-backup.hg
Traceback similar to already posted: http://bpaste.net/show/91435/

 WAT?

 % hg out            

набор изм-й:   18903:35111d556de8
закладка:      zsh
автор:         Nikolaj Sjujskij <sterkrig@myopera.com>
дата:          Mon Apr 08 16:51:38 2013 +0400
сводка:        zsh_completion: make use of `debuglabelcomplete` command

набор изм-й:   18944:4d9daa13d870
метка:         tip
автор:         Nikolaj Sjujskij <sterkrig@myopera.com>
дата:          Tue Apr 09 19:58:04 2013 +0400
сводка:        zsh_completion: make use of `debugpathcomplete` command

Revision numbers have changed.

`hg rebase -s 18944 -d @` went all right.

I have this bundle, but:
 % hg in ../bd30c1ae9357-backup.hg
comparing with ../bd30c1ae9357-backup.hg
abort: 00changelog.i@35111d556de8: unknown parent!

Even within *another* repo where I pulled all the other strip-backups created today, which were not much help:

 % hg out                         
changeset:   18943:97b2b6d02687
parent:      18912:4e1ae55e63ef
user:        Nikolaj Sjujskij <sterkrig@myopera.com>
date:        Tue Apr 09 19:58:04 2013 +0400
summary:     zsh_completion: make use of `debugpathcomplete` command

changeset:   18944:4d9daa13d870
tag:         tip
parent:      18942:6891e361bec6
user:        Nikolaj Sjujskij <sterkrig@myopera.com>
date:        Tue Apr 09 19:58:04 2013 +0400
summary:     zsh_completion: make use of `debugpathcomplete` command

I'm running current default tip (updated regularly), and don't use evolve.
But those two changesets were `histedit`ed several times.

I've succesfully built a stable repo. Expect detail and probable fix soon.

fix send to the list

Fixed by http://selenic.com/repo/hg/rev/31bcc5112191
Pierre-Yves David <pierre-yves.david@logilab.fr>
destroyed: invalidate phraserevs cache in all case (issue3858)

When revisions are destroyed, the `phaserevs` cache becomes invalid in most case.
This cache hold a `{rev => phase}` mapping and revision number most likely
changed.

Since 1c8e0d6ac3b0, we filter unknown phases' roots after changesets
destruction.  When some roots are filtered the `phaserevs` cache is invalidated.
But not if none root where destroyed.

We now invalidate the cache in all case filtered root or not.

This bug was a bit tricky to reproduce as in most case we either:
* rebase a set a draft changeset including root (phaserev invalidated)
* strip tip-most changesets (no re-numbering of revision)

Note that the invalidation of `phaserevs` are not strictly needed when only
tip-most part of the history have been destroyed. But I do not expect the
overhead to be significant.

(please test the fix)

Could you please point me to Mercurial nightly build (already compiled version) for Windows?

http://code.google.com/p/mercurial-nightly-builds/downloads/list seems outdated.

Try this:

http://mercurial.selenic.com/wiki/HackableMercurial

Doesn't look like nightly build. I will wait for next release of Mercurial and let you know.

The bug is fixed in Mercurial 2.6-RC. Thank you!

Many thanks to all involved!

*** Bug 3944 has been marked as a duplicate of this bug. ***

reopened with no explanation, reclosing.