wthidden / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

transaction abort #137

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by philip.r...@gmail.com on 10 May 2012 at 2:56

GoogleCodeExporter commented 8 years ago
Sorry, apparently I don't know how to use a web form.

What steps will reproduce the problem?
1. Open a terminal and run the following command (with Mercurial installed):
  hg clone https://googlefontdirectory.googlecode.com/hg/ googlefontdirectory

What is the expected output? What do you see instead?
I expect the repo to cloned successfully, instead I get:

  $ hg clone https://googlefontdirectory.googlecode.com/hg/ googlefontdirectory
    requesting all changes
    adding changesets
    adding manifests
    adding file changes
    transaction abort!
    rollback completed
    abort: connection ended unexpectedly

What version of the product are you using? On what operating system?
Mercurial 1.4.3 on Kubuntu 11.10

Original comment by philip.r...@gmail.com on 10 May 2012 at 3:00

GoogleCodeExporter commented 8 years ago
NOTE: A lot of time passes between `adding file changes` and `transaction 
abort!`.

Original comment by philip.r...@gmail.com on 10 May 2012 at 3:01

GoogleCodeExporter commented 8 years ago
OK, I was able to get around this by pulling the repository by chunk.  I did 
this by browsing a way back in the changes to find an old revision number and 
then pulling that.  I then did a pull to get the latest changes.  Here are the 
commands I used.  Your mileage may vary.

  $ hg clone -r ef7e2aad502f https://googlefontdirectory.googlecode.com/hg/ googlefontdirectory
  $ cd googlefontdirectory/
  $ hg pull -u

Original comment by philip.r...@gmail.com on 10 May 2012 at 3:34

GoogleCodeExporter commented 8 years ago
Thanks for posting your fix! Sadly this is caused by some kind of network error 
I think - it sometimes happens to me too, and I try again later and it works :)

Original comment by dcrossland@google.com on 10 May 2012 at 4:27