Cloning the Adium repo

[Robert Vehse]

Content preview: Hi everyone, Recently, I twice tried to download Adium source
from our repo and each time the download timed out. Yesterday, a user reported
cloning didn’t work for them either (https://www.facebook.com/permalink.php?story_fbid153957981491819&ide21951818&comment_id153987753641819&reply_comment_id153987939626819&comment_tracking=%7B%22tn%22%3A%22R5%22%7D).
[...]

Content analysis details: (-0.1 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(robertvehse[at]fastmail.fm)
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Spam-Flag: NO
X-BeenThere: ***@adium.im
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Adium Development List <devel.adium.im>
List-Unsubscribe: <http://adium.im/mailman/options/devel_adium.im>,
<mailto:devel-***@adium.im?subject=unsubscribe>
List-Archive: <http://adium.im/pipermail/devel_adium.im/>
List-Post: <mailto:***@adium.im>
List-Help: <mailto:devel-***@adium.im?subject=help>
List-Subscribe: <http://adium.im/mailman/listinfo/devel_adium.im>,
<mailto:devel-***@adium.im?subject=subscribe>
Reply-To: Adium Development List <***@adium.im>
Errors-To: devel-***@adium.im
Sender: "devel" <devel-***@adium.im>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - duck
X-AntiAbuse: Original Domain - ml-in.narkive.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - adium.im
X-Get-Message-Sender-Via: duck: acl_c_authenticated_local_user: mailman/mailman
X-Authenticated-Sender: duck: ***@adium.im
X-Source:
X-Source-Args:
X-Source-Dir:

Hi everyone,

Recently, I twice tried to download Adium source from our repo and each time the download timed out. Yesterday, a user reported cloning didn’t work for them either (https://www.facebook.com/permalink.php?story_fbid=10153957981491819&id=6521951818&comment_id=10153987753641819&reply_comment_id=10153987939626819&comment_tracking=%7B%22tn%22%3A%22R5%22%7D).

For now, should we perhaps only point to Bitbucket at https://trac.adium.im/wiki/GettingNewestAdiumSource (and possibly other places)?

Regards,
Robbie

[Matthew]

It worked for me:

Naitaka:~ mathuaerknedam$ hg clone https://hg.adium.im/adium scr/adium-new

warning: connecting to hg.adium.im using legacy security technology
(TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for
more info

warning: connecting to hg.adium.im using legacy security technology
(TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for
more info

warning: connecting to hg.adium.im using legacy security technology
(TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for
more info

requesting all changes

warning: connecting to hg.adium.im using legacy security technology
(TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for
more info

adding changesets

adding manifests

adding file changes

added 5951 changesets with 69292 changes to 34410 files (+10 heads)

warning: connecting to hg.adium.im using legacy security technology
(TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for
more info

updating to branch default

6538 files updated, 0 files merged, 0 files removed, 0 files unresolved

Post by Robert Vehse
Hi everyone,
Recently, I twice tried to download Adium source from our repo and each time the download timed out. Yesterday, a user reported cloning didn’t work for them either (https://www.facebook.com/permalink.php?story_fbid=10153957981491819&id=6521951818&comment_id=10153987753641819&reply_comment_id=10153987939626819&comment_tracking=%7B%22tn%22%3A%22R5%22%7D).
For now, should we perhaps only point to Bitbucket at https://trac.adium.im/wiki/GettingNewestAdiumSource (and possibly other places)?
Regards,
Robbie

[Robert Vehse]

I reckon your bandwidth is a lot higher than mine? I'd been downloading for 20 to 30 minutes when it failed.

[Augie Fackler]

clonebundles extension - advertise pre-generated bundles to seed clones
"clonebundles" is a server-side extension used to advertise the existence of
pre-generated, externally hosted bundle files to clients that are cloning so
that cloning can be faster, more reliable, and require less resources on the
server.

[...]

This extension provides server operators the ability to offload potentially
expensive clone load to an external service. Here's how it works.
1. A server operator establishes a mechanism for making bundle files available
on a hosting service where Mercurial clients can fetch them.
2. A manifest file listing available bundle URLs and some optional metadata is
added to the Mercurial repository on the server.
3. A client initiates a clone against a clone bundles aware server.
4. The client sees the server is advertising clone bundles and fetches the
manifest listing available bundles.
5. The client filters and sorts the available bundles based on what it
supports and prefers.
6. The client downloads and applies an available bundle from the server-
specified URL.
7. The client reconnects to the original server and performs the equivalent of
'hg pull' to retrieve all repository data not in the bundle. (The
repository could have been updated between when the bundle was created and
when the client started the clone.)
Instead of the server generating full repository bundles for every clone
request, it generates full bundles once and they are subsequently reused to
bootstrap new clones. The server may still transfer data at clone time.
However, this is only data that has been added/changed since the bundle was
created. For large, established repositories, this can reduce server load for
clones to less than 1% of original.
I reckon your bandwidth is a lot higher than mine? I'd been downloading for 20 to 30 minutes when it failed.