amp pull -u fails with strange errors
Reported by seydar | November 25th, 2009 @ 03:22 AM
I award ourselves no points. I don't really know what to say for this one. Tiger/PPC 10.4.11 running amp C#66 (commit # 66)
[ari: ~/src/amp.code] amp pull -u status: pulling from https://seydar:***@bitbucket.org/carbonica/amp
status: searching for changes
status: adding changeset
bignum too big to convert into long'<br/>
/Users/ari/src/amp.code/lib/amp/revlogs/changelog.rb:84:in[]'
/Users/ari/src/amp.code/lib/amp/revlogs/changelog.rb:84:in
read'
/Users/ari/src/amp.code/lib/amp/revlogs/revlog.rb:587:inload_cache'
/Users/ari/src/amp.code/lib/amp/revlogs/revlog.rb:615:in
get_chunk'
/Users/ari/src/amp.code/lib/amp/revlogs/revlog.rb:684:indecompress_revision'
/Users/ari/src/amp.code/lib/amp/revlogs/revlog.rb:915:in
add_group'
/Users/ari/src/amp.code/lib/amp/revlogs/changegroup.rb:54:ineach_chunk'
/Users/ari/src/amp.code/lib/amp/revlogs/revlog.rb:881:in
add_group'
/Users/ari/src/amp.code/lib/amp/repository/repositories/local_repository.rb:581:inadd_changegroup'
/Users/ari/src/amp.code/lib/amp/repository/journal.rb:23:in
start'
/Users/ari/src/amp.code/lib/amp/repository/repositories/local_repository.rb:576:inadd_changegroup'
/Users/ari/src/amp.code/lib/amp/repository/repositories/local_repository.rb:539:in
pull'
/Users/ari/src/amp.code/lib/amp/repository/repositories/local_repository.rb:212:inlock_store'
/Users/ari/src/amp.code/lib/amp/repository/repositories/local_repository.rb:510:in
pull'
/Users/ari/src/amp.code/lib/amp/commands/commands/workflows/hg/pull.rb:51
/Users/ari/src/amp.code/lib/amp/commands/command.rb:461:in[]'
/Users/ari/src/amp.code/lib/amp/commands/command.rb:461:in
run'
/Users/ari/src/amp.code/lib/amp/commands/dispatch.rb:126:inrun'
/Users/ari/src/amp.code/lib/amp/support/support.rb:222:in
full_backtrace_please'
/Users/ari/src/amp.code/lib/amp/commands/dispatch.rb:125:inrun'
/Users/ari/src/amp.code/bin/amp:30 status: adding manifests
status: adding file changes
Operation aborted.
abort: received file revlog group is empty
[ari: ~/src/amp.code]
Comments and changes to this ticket
-
Michael J. Edgar November 25th, 2009 @ 08:27 AM
- Assigned user set to “Michael J. Edgar”
- State changed from “new” to “open”
Difficult to reproduce this. Gonna have to stare at the source for a while, first.
-
Michael J. Edgar November 25th, 2009 @ 08:50 AM
Difficult to reproduce this. Gonna have to stare at the source for a while, first.
-
seydar November 28th, 2009 @ 06:09 AM
I've got a more specific issue with pull. Lookit: http://pastie.org/717902
I'm looking at this and hoping that fixing this will fix the above. It is a bug in
amp pull, specifically line 607 in local_repository.rb -
seydar November 28th, 2009 @ 06:15 AM
I managed to fix that bug, but there is still an issue with the finalizer in zlib. Could you take a look at that?
-
Michael Edgar November 28th, 2009 @ 01:22 PM
seydar: open a fresh ticket for the problems with finalizer in zlib. Can you post a trace/repro, as well?
Also, is it zlib or bz2?
Will look at pull today when I get back from thanksgiving.
-
Michael J. Edgar December 5th, 2009 @ 05:07 PM
- State changed from “open” to “resolved”
It appears this bug has been fixed, so this ticket is resolved. Seydar: re-open if it actually isn't.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Rethink Version Control.- http://amp.carboni.ca/
Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.
Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.
Michael J. Edgar