2007-09-11 05:03:00 +02:00
|
|
|
#ifndef FETCH_PACK_H
|
|
|
|
|
#define FETCH_PACK_H
|
|
|
|
|
|
2012-09-09 08:19:40 +02:00
|
|
|
#include "string-list.h"
|
2013-07-08 22:56:53 +02:00
|
|
|
#include "run-command.h"
|
2012-09-09 08:19:40 +02:00
|
|
|
|
2011-03-16 08:08:34 +01:00
|
|
|
struct fetch_pack_args {
|
2007-09-11 05:03:00 +02:00
|
|
|
const char *uploadpack;
|
|
|
|
|
int unpacklimit;
|
|
|
|
|
int depth;
|
2007-09-18 10:55:00 +02:00
|
|
|
unsigned quiet:1,
|
|
|
|
|
keep_pack:1,
|
2007-09-19 06:49:35 +02:00
|
|
|
lock_pack:1,
|
2007-09-18 10:55:00 +02:00
|
|
|
use_thin_pack:1,
|
|
|
|
|
fetch_all:1,
|
fetch-pack: new --stdin option to read refs from stdin
If a remote repo has too many tags (or branches), cloning it over the
smart HTTP transport can fail because remote-curl.c puts all the refs
from the remote repo on the fetch-pack command line. This can make the
command line longer than the global OS command line limit, causing
fetch-pack to fail.
This is especially a problem on Windows where the command line limit is
orders of magnitude shorter than Linux. There are already real repos out
there that msysGit cannot clone over smart HTTP due to this problem.
Here is an easy way to trigger this problem:
git init too-many-refs
cd too-many-refs
echo bla > bla.txt
git add .
git commit -m test
sha=$(git rev-parse HEAD)
tag=$(perl -e 'print "bla" x 30')
for i in `seq 50000`; do
echo $sha refs/tags/$tag-$i >> .git/packed-refs
done
Then share this repo over the smart HTTP protocol and try cloning it:
$ git clone http://localhost/.../too-many-refs/.git
Cloning into 'too-many-refs'...
fatal: cannot exec 'fetch-pack': Argument list too long
50k tags is obviously an absurd number, but it is required to
demonstrate the problem on Linux because it has a much more generous
command line limit. On Windows the clone fails with as little as 500
tags in the above loop, which is getting uncomfortably close to the
number of tags you might see in real long lived repos.
This is not just theoretical, msysGit is already failing to clone our
company repo due to this. It's a large repo converted from CVS, nearly
10 years of history.
Four possible solutions were discussed on the Git mailing list (in no
particular order):
1) Call fetch-pack multiple times with smaller batches of refs.
This was dismissed as inefficient and inelegant.
2) Add option --refs-fd=$n to pass a an fd from where to read the refs.
This was rejected because inheriting descriptors other than
stdin/stdout/stderr through exec() is apparently problematic on Windows,
plus it would require changes to the run-command API to open extra
pipes.
3) Add option --refs-from=$tmpfile to pass the refs using a temp file.
This was not favored because of the temp file requirement.
4) Add option --stdin to pass the refs on stdin, one per line.
In the end this option was chosen as the most efficient and most
desirable from scripting perspective.
There was however a small complication when using stdin to pass refs to
fetch-pack. The --stateless-rpc option to fetch-pack also uses stdin for
communication with the remote server.
If we are going to sneak refs on stdin line by line, it would have to be
done very carefully in the presence of --stateless-rpc, because when
reading refs line by line we might read ahead too much data into our
buffer and eat some of the remote protocol data which is also coming on
stdin.
One way to solve this would be to refactor get_remote_heads() in
fetch-pack.c to accept a residual buffer from our stdin line parsing
above, but this function is used in several places so other callers
would be burdened by this residual buffer interface even when most of
them don't need it.
In the end we settled on the following solution:
If --stdin is specified without --stateless-rpc, fetch-pack would read
the refs from stdin one per line, in a script friendly format.
However if --stdin is specified together with --stateless-rpc,
fetch-pack would read the refs from stdin in packetized format
(pkt-line) with a flush packet terminating the list of refs. This way we
can read the exact number of bytes that we need from stdin, and then
get_remote_heads() can continue reading from the same fd without losing
a single byte of remote protocol data.
This way the --stdin option only loses generality and scriptability when
used together with --stateless-rpc, which is not easily scriptable
anyway because it also uses pkt-line when talking to the remote server.
Signed-off-by: Ivan Todoroski <grnch@gmx.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-04-02 17:13:48 +02:00
|
|
|
stdin_refs:1,
|
2007-09-18 10:55:00 +02:00
|
|
|
verbose:1,
|
2008-03-04 04:27:33 +01:00
|
|
|
no_progress:1,
|
2009-10-31 01:47:42 +01:00
|
|
|
include_tag:1,
|
2013-05-26 03:16:17 +02:00
|
|
|
stateless_rpc:1,
|
|
|
|
|
check_self_contained_and_connected:1,
|
|
|
|
|
self_contained_and_connected:1;
|
2007-09-11 05:03:00 +02:00
|
|
|
};
|
|
|
|
|
|
2012-09-09 08:19:43 +02:00
|
|
|
/*
|
2013-01-29 23:02:15 +01:00
|
|
|
* sought represents remote references that should be updated from.
|
|
|
|
|
* On return, the names that were found on the remote will have been
|
|
|
|
|
* marked as such.
|
2012-09-09 08:19:43 +02:00
|
|
|
*/
|
2007-09-19 06:49:35 +02:00
|
|
|
struct ref *fetch_pack(struct fetch_pack_args *args,
|
2012-09-09 08:19:39 +02:00
|
|
|
int fd[], struct child_process *conn,
|
|
|
|
|
const struct ref *ref,
|
|
|
|
|
const char *dest,
|
2013-01-29 23:02:15 +01:00
|
|
|
struct ref **sought,
|
|
|
|
|
int nr_sought,
|
2012-09-09 08:19:39 +02:00
|
|
|
char **pack_lockfile);
|
2007-09-11 05:03:00 +02:00
|
|
|
|
|
|
|
|
#endif
|