ScopeReplacer object '_parse_limit' was used incorrectly

[Aliaksei Vasileuski]

I executed "undelete foo/bar --limit 1000" two times and got:
ScopeReplacer object '_parse_limit' was used incorrectly: Object already cleaned up, did you assign it to another variable?: _factory

BTW "foo/bar" directory was deleted with all contained files.

[Parth Malwankar (parthm)]

Below is what I tried. Its seems to work. Can you provide a simple use case that leads to the above error.

[foobar]% bzr mkdir xyz
added xyz
[foobar]% echo "hello" > xyz/file0
[foobar]% bzr add xyz/file0
adding xyz/file0
[foobar]% bzr ci -m "added xyz/file0"
Committing to: /home/parthm/tmp/foobar/
added xyz
added xyz/file0
Committed revision 5.
[foobar]% bzr rm xyz
deleted xyz/file0
deleted xyz
[foobar]% bzr ci -m "xyz removed"
Committing to: /home/parthm/tmp/foobar/
deleted xyz
deleted xyz/file0
Committed revision 6.
[foobar]% bzr undelete xyz
[foobar]% bzr st
added:
  xyz/
  xyz/file0
[foobar]% bzr undelete xyz
nothing to do for 'xyz'
[foobar]%

[Aliaksei Vasileuski (sagara1337)]

Deleted directory should be past "--limit", so bzr undelete will say "you could look deeper in the history using the --limit option.".
Also "--limit" option must be used, without it I have no error (folder is just not found).

As for the simple use case, I didn't managed to reproduce it, but I will try again.

[Aliaksei Vasileuski (sagara1337)]

Also I execute commands from bzr shell, that's mandatory to reproduce.
Also I changed "rm xyz" => "rm xyz/file0 xyz":

So steps to reproduce:
mkdir foo
cd foo
bzr shell

And inside "bzr shell":
init
mkdir xyz
echo "hello" > xyz/file0
add
ci -m "added xyz/file0"
del xyz/file0 xyz (I run on Windows, "rm" for GNU OS)
ci -m "xyz removed"
ci --unchanged -m "bla"
ci --unchanged -m "bla bla"
undelete xyz --limit 2
undelete xyz --limit 2