Bug 3017 - Remote push to empty repository results in overflow error
Summary: Remote push to empty repository results in overflow error
Status: RESOLVED FIXED
Alias: None
Product: Mercurial
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: unspecified
Hardware: All All
: urgent bug
Assignee: Bugzilla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 06:22 UTC by Peter Haase
Modified: 2012-05-13 05:00 UTC (History)
3 users (show)

See Also:
Python Version: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Haase 2011-09-21 06:22 UTC
When pushing from an 1.9.2 client (Windows XP) to an 1.9.2 server (SuSe 
11.2) into an empty repository, the following error message occurs:

pushing to http://maid5054/hg/my-project
searching for changes
** unknown exception encountered, please report by visiting
**  http://mercurial.selenic.com/wiki/BugTracker
** Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit 
(Intel)]
** Mercurial Distributed SCM (version 1.9.2)
** Extensions loaded: notify, graphlog, hgk, progress, rebase, mq, convert
Traceback (most recent call last):
  File "hg", line 42, in <module>
  File "mercurial\dispatch.pyo", line 27, in run
  File "mercurial\dispatch.pyo", line 64, in dispatch
  File "mercurial\dispatch.pyo", line 87, in _runcatch
  File "mercurial\dispatch.pyo", line 688, in _dispatch
  File "mercurial\dispatch.pyo", line 463, in runcommand
  File "mercurial\dispatch.pyo", line 742, in _runcommand
  File "mercurial\dispatch.pyo", line 696, in checkargs
  File "mercurial\dispatch.pyo", line 685, in <lambda>
  File "mercurial\util.pyo", line 385, in check
  File "mercurial\extensions.pyo", line 137, in wrap
  File "mercurial\util.pyo", line 385, in check
  File "hgext\mq.pyo", line 3218, in mqcommand
  File "mercurial\util.pyo", line 385, in check
  File "mercurial\commands.pyo", line 3886, in push
  File "mercurial\localrepo.pyo", line 1424, in push
  File "mercurial\wireproto.pyo", line 300, in unbundle
  File "mercurial\httprepo.pyo", line 194, in _callpush
  File "mercurial\httprepo.pyo", line 164, in _call
  File "mercurial\httprepo.pyo", line 79, in _callstream
OverflowError: long int too large to convert to int
Comment 1 kiilerix 2011-09-21 06:35 UTC
Are you pushing a big repo? What is the size of the bundle created by

  hg bundle --base null all.hg
Comment 2 Peter Haase 2011-09-21 09:23 UTC
> Mads Kiilerich <mads@kiilerich.com> added the comment:
> 
> Are you pushing a big repo? What is the size of the bundle created by
> 
>   hg bundle --base null all.hg

Repo size is approx. 2 GB. 

Pushing it step by step (approx. 1000 changesets per step) works fine!
---
This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records.

Diese Nachricht enthält vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfänger dieser E-mail sein, senden Sie bitte diese an den Absender zurück und löschen Sie die E-mail aus Ihrem System.
Comment 3 kiilerix 2011-09-21 09:29 UTC
It makes a big difference on what side of 2 GB it is - but I assume it is >
2 GB. In that case it is a regression introduced in 1.9 and should be fixed
in next bugfix release. Another workaround could be to use 1.8.4.
Comment 4 Peter Haase 2011-09-22 05:22 UTC
Actually it's slightly above 2 GB! The workaround not pushing the repository at once works well for me.

Thanks for the help!

---
This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records.

Diese Nachricht enthält vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfänger dieser E-mail sein, senden Sie bitte diese an den Absender zurück und löschen Sie die E-mail aus Ihrem System.
Comment 5 HG Bot 2011-09-27 18:00 UTC
Fixed by http://selenic.com/repo/hg/rev/94b200a11cf7
Mads Kiilerich <mads@kiilerich.com>
http: handle push of bundles > 2 GB again (issue3017)

(please test the fix)
Comment 6 Bugzilla 2012-05-12 09:23 UTC

--- Bug imported by bugzilla@serpentine.com 2012-05-12 09:23 EDT  ---

This bug was previously known as _bug_ 3017 at http://mercurial.selenic.com/bts/issue3017