Re: [PATCH v2 02/10] builtin/cat-file: wire up an option to filter objects
- From
Karthik Nayak <karthik.188@gmail.com>
- Date
- Apr 1, 2025, 12:05 UTC
- Message-ID
- <CAOLa=ZTgU+E3Y6DRCA0EOg9uOvNoggCRPBNYjDZTOinaDVj95Q@mail.gmail.com>
- In-Reply-To
- <20250327-pks-cat-file-object-type-filter-v2-2-4bbc7085d7c5@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
> In batch mode, git-cat-file(1) enumerates all objects and prints them > by iterating through both loose and packed objects. This works without
Nit: I assume you're referring to the `--batch-all-objects` mode. So would be nice to specify here perhaps?
Show 44 quoted lines
> considering their reachability at all, and consequently most options to > filter objects as they exist in e.g. git-rev-list(1) are not applicable. > In some situations it may still be useful though to filter objects based > on properties that are inherent to them. This includes the object size > as well as its type. > > Such a filter already exists in git-rev-list(1) with the `--filter=` > command line option. While this option supports a couple of filters that > are not applicable to our usecase, some of them are quite a neat fit. > > Wire up the filter as an option for git-cat-file(1). This allows us to > reuse the same syntax as in git-rev-list(1) so that we don't have to > reinvent the wheel. For now, we die when any of the filter options has > been passed by the user, but they will be wired up in subsequent > commits. > > Further note that the filters that we are about to introduce don't > significantly speed up the runtime of git-cat-file(1). While we can skip > emitting a lot of objects in case they are uninteresting to us, the > majority of time is spent reading the packfile, which is bottlenecked by > I/O and not the processor. This will change though once we start to make > use of bitmaps, which will allow us to skip reading the whole packfile. > > Signed-off-by: Patrick Steinhardt <ps@pks.im> > --- > Documentation/git-cat-file.adoc | 6 ++++++ > builtin/cat-file.c | 37 +++++++++++++++++++++++++++++++++---- > t/t1006-cat-file.sh | 32 ++++++++++++++++++++++++++++++++ > 3 files changed, 71 insertions(+), 4 deletions(-) > > diff --git a/Documentation/git-cat-file.adoc b/Documentation/git-cat-file.adoc > index d5890ae3686..f7f57b7f538 100644 > --- a/Documentation/git-cat-file.adoc > +++ b/Documentation/git-cat-file.adoc > @@ -81,6 +81,12 @@ OPTIONS > end-of-line conversion, etc). In this case, `<object>` has to be of > the form `<tree-ish>:<path>`, or `:<path>`. > > +--filter=<filter-spec>:: > +--no-filter:: > + Omit objects from the list of printed objects. This can only be used in > + combination with one of the batched modes. The '<filter-spec>' may be > + one of the following: > +
Shouldn't we say this is specific to `--batch-all-objects`?
Show 34 quoted lines
> --path=<path>::
> For use with `--textconv` or `--filters`, to allow specifying an object
> name and a path separately, e.g. when it is difficult to figure out
> diff --git a/builtin/cat-file.c b/builtin/cat-file.c
> index 8e40016dd24..940900d92ad 100644
> --- a/builtin/cat-file.c
> +++ b/builtin/cat-file.c
> @@ -15,6 +15,7 @@
> #include "gettext.h"
> #include "hex.h"
> #include "ident.h"
> +#include "list-objects-filter-options.h"
> #include "parse-options.h"
> #include "userdiff.h"
> #include "streaming.h"
> @@ -35,6 +36,7 @@ enum batch_mode {
> };
>
> struct batch_options {
> + struct list_objects_filter_options objects_filter;
> int enabled;
> int follow_symlinks;
> enum batch_mode batch_mode;
> @@ -487,6 +489,13 @@ static void batch_object_write(const char *obj_name,
> return;
> }
>
> + switch (opt->objects_filter.choice) {
> + case LOFC_DISABLED:
> + break;
> + default:
> + BUG("unsupported objects filter");
> + }
> +Okay here it seems like it also applies to other batch modes. So it would be nice to perhaps clarify how this works when not used with `--batch-all-objects`?
Show 94 quoted lines
> if (use_mailmap && (data->type == OBJ_COMMIT || data->type == OBJ_TAG)) {
> size_t s = data->size;
> char *buf = NULL;
> @@ -812,7 +821,8 @@ static int batch_objects(struct batch_options *opt)
> struct object_cb_data cb;
> struct object_info empty = OBJECT_INFO_INIT;
>
> - if (!memcmp(&data.info, &empty, sizeof(empty)))
> + if (!memcmp(&data.info, &empty, sizeof(empty)) &&
> + opt->objects_filter.choice == LOFC_DISABLED)
> data.skip_object_info = 1;
>
> if (repo_has_promisor_remote(the_repository))
> @@ -936,10 +946,13 @@ int cmd_cat_file(int argc,
> int opt_cw = 0;
> int opt_epts = 0;
> const char *exp_type = NULL, *obj_name = NULL;
> - struct batch_options batch = {0};
> + struct batch_options batch = {
> + .objects_filter = LIST_OBJECTS_FILTER_INIT,
> + };
> int unknown_type = 0;
> int input_nul_terminated = 0;
> int nul_terminated = 0;
> + int ret;
>
> const char * const builtin_catfile_usage[] = {
> N_("git cat-file <type> <object>"),
> @@ -1000,6 +1013,8 @@ int cmd_cat_file(int argc,
> N_("run filters on object's content"), 'w'),
> OPT_STRING(0, "path", &force_path, N_("blob|tree"),
> N_("use a <path> for (--textconv | --filters); Not with 'batch'")),
> + OPT_CALLBACK(0, "filter", &batch.objects_filter, N_("args"),
> + N_("object filtering"), opt_parse_list_objects_filter),
> OPT_END()
> };
>
> @@ -1014,6 +1029,14 @@ int cmd_cat_file(int argc,
> if (use_mailmap)
> read_mailmap(&mailmap);
>
> + switch (batch.objects_filter.choice) {
> + case LOFC_DISABLED:
> + break;
> + default:
> + usagef(_("objects filter not supported: '%s'"),
> + list_object_filter_config_name(batch.objects_filter.choice));
> + }
> +
> /* --batch-all-objects? */
> if (opt == 'b')
> batch.all_objects = 1;
> @@ -1068,7 +1091,8 @@ int cmd_cat_file(int argc,
> usage_msg_opt(_("batch modes take no arguments"), builtin_catfile_usage,
> options);
>
> - return batch_objects(&batch);
> + ret = batch_objects(&batch);
> + goto out;
> }
>
> if (opt) {
> @@ -1097,5 +1121,10 @@ int cmd_cat_file(int argc,
>
> if (unknown_type && opt != 't' && opt != 's')
> die("git cat-file --allow-unknown-type: use with -s or -t");
> - return cat_one_file(opt, exp_type, obj_name, unknown_type);
> +
> + ret = cat_one_file(opt, exp_type, obj_name, unknown_type);
> +
> +out:
> + list_objects_filter_release(&batch.objects_filter);
> + return ret;
> }
> diff --git a/t/t1006-cat-file.sh b/t/t1006-cat-file.sh
> index 398865d6ebe..1246d3119f8 100755
> --- a/t/t1006-cat-file.sh
> +++ b/t/t1006-cat-file.sh
> @@ -1353,4 +1353,36 @@ test_expect_success PERL '--batch-command info is unbuffered by default' '
> perl -e "$script" -- --batch-command $hello_oid "$expect" "info "
> '
>
> +test_expect_success 'setup for objects filter' '
> + git init repo
> +'
> +
> +test_expect_success 'objects filter with unknown option' '
> + cat >expect <<-EOF &&
> + fatal: invalid filter-spec ${SQ}unknown${SQ}
> + EOF
> + test_must_fail git -C repo cat-file --filter=unknown 2>err &&
> + test_cmp expect err
> +'
> +Would it be also worthwhile to test the `--no-filter` option?
Show 24 quoted lines
> +for option in blob:none blob:limit=1 object:type=tag sparse:oid=1234 tree:1 sparse:path=x
> +do
> + test_expect_success "objects filter with unsupported option $option" '
> + case "$option" in
> + tree:1)
> + echo "usage: objects filter not supported: ${SQ}tree${SQ}" >expect
> + ;;
> + sparse:path=x)
> + echo "fatal: sparse:path filters support has been dropped" >expect
> + ;;
> + *)
> + option_name=$(echo "$option" | cut -d= -f1) &&
> + printf "usage: objects filter not supported: ${SQ}%s${SQ}\n" "$option_name" >expect
> + ;;
> + esac &&
> + test_must_fail git -C repo cat-file --filter=$option 2>err &&
> + test_cmp expect err
> + '
> +done
> +
> test_done
>
> --
> 2.49.0.472.ge94155a9ec.dirty