[Bug 6933] New: hg push timeout when evolve is enabled
mercurial-bugs at mercurial-scm.org
mercurial-bugs at mercurial-scm.org
Tue Oct 29 10:45:29 UTC 2024
https://bz.mercurial-scm.org/show_bug.cgi?id=6933
Bug ID: 6933
Summary: hg push timeout when evolve is enabled
Product: Mercurial
Version: 6.8.1
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: evolution
Assignee: bugzilla at mercurial-scm.org
Reporter: gklittlejohn at googlemail.com
CC: mercurial-devel at mercurial-scm.org,
pierre-yves.david at ens-lyon.org
Python Version: ---
This is using evolve 11.1.4. Evolve is enabled on a mercurial server to get
pullbundles to work. The repository I am seeing this to is large with a long
history.
The changes get pushed but the mercurial client hits a timeout.
The mercurial client is 6.6.3 on Windows.
% hg push --debug --rev 21049 https://...
pushing to https://...
using https://...
sending capabilities command
query 1; heads
sending batch command
searching for changes
all remote heads known locally
preparing listkeys for "phases"
sending listkeys command
received listkey for "phases": 15 bytes
checking for updated bookmarks
preparing listkeys for "bookmarks"
sending listkeys command
received listkey for "bookmarks": 0 bytes
preparing listkeys for "namespaces"
sending listkeys command
received listkey for "namespaces": 40 bytes
preparing listkeys for "phases"
sending listkeys command
received listkey for "phases": 15 bytes
sending branchmap command
preparing listkeys for "bookmarks"
sending listkeys command
received listkey for "bookmarks": 0 bytes
2 changesets found
list of changesets:
38699bcaff4fcec96bde10e8dd1982ea30ddb0e1
5b8f2b324af53fc6ca08fc6aba3786c766faea94
bundle2-output-bundle: "HG20", 5 parts total
bundle2-output-part: "replycaps" 210 bytes payload
bundle2-output-part: "check:phases" 24 bytes payload
bundle2-output-part: "check:updated-heads" streamed payload
bundle2-output-part: "changegroup" (params: 1 mandatory) streamed payload
bundle2-output-part: "phase-heads" 24 bytes payload
sending unbundle command
sending 8470 bytes
(sent 9 HTTP requests and 11257 bytes; received 817 bytes in responses)
HTTP Error: 504 (Gateway Time-out)
[command returned code 255 Tue Oct 29 10:22:41 2024]
I note the Mercurial pullbundles tests have the following configuration rather
than the evolve extension:
[experimental]
evolution = True
This alternate configuration does not exhibit the timeout issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list