From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-11.5 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS, USER_IN_DEF_DKIM_WL shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 8C4391F9F4 for ; Tue, 5 Oct 2021 00:20:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230369AbhJEAVq (ORCPT ); Mon, 4 Oct 2021 20:21:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46454 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230271AbhJEAVq (ORCPT ); Mon, 4 Oct 2021 20:21:46 -0400 Received: from mail-pf1-x44a.google.com (mail-pf1-x44a.google.com [IPv6:2607:f8b0:4864:20::44a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7CB44C061745 for ; Mon, 4 Oct 2021 17:19:56 -0700 (PDT) Received: by mail-pf1-x44a.google.com with SMTP id t4-20020a62ea04000000b0044b333f5d1bso9979197pfh.20 for ; Mon, 04 Oct 2021 17:19:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:in-reply-to:message-id:mime-version:references:subject:from:to :cc; bh=gCcN3OjOStawLoGGgqtCJg0NEtHKqK3MkfEr5Vuqtk4=; b=lZAuRJI5Ikzw/9XR2ksM5q88V9nk19IFcfJfDGbdsPA3Ddj31Gf60jPIYraE2zgcjf KsKdOExi5UNkQIU/jHr8Mr7+iXRVLEiz/EYLgjae2SHDCgCW2JGQ5kDt/NeqzIGbokHk GMfTKXnGJP6HqfRabSQupz0iytJeaFudV21lf4ytje2mp0Wm17+iqDj1tW76ICxPQiY4 QEObKz0/fyHAylJLG/oL4cuysxLw+BMJ55QaZxqacdl3h0sI1hOC6klUudKBxcJ52KZQ vV9bhPGc4MIC694sRxVHdxvVCpSV6vV2XhNKPyhj20NIv8Qw3dMvLlCDTnsH1Q7e02KZ mM8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:in-reply-to:message-id:mime-version :references:subject:from:to:cc; bh=gCcN3OjOStawLoGGgqtCJg0NEtHKqK3MkfEr5Vuqtk4=; b=PYIkffzHiJer7tdkSwvEr6tW+eyykvhm4/2eQXsPFk/mWeg5x4khmHtMQbCg3fiWcl vTQtmv5xafLiQ+qqiUbTBMJdjLIYh6rR35YoUv6xURNmeSBmWpFaw37pWP/koWZYl6QA ax3O1PTR4YZ1k1bpmVl6ebFvvgoxPc6WstG8VDt9/i6fbDWa7x2p81FiC6g2flR8bY+k cCqZhyIi8VYlQMRZlVfKGHqkRORpoglXuPckdb673bdjxV/QL81lxVjUou7OMGCvnwFR Bi8TWLG/UPhALfx91G+LOqGl6X7w6Yr+MNll2MpT5hRzICjxoatB3ONPrOWVrkog7M7z ms1Q== X-Gm-Message-State: AOAM530iM+yYCpLITtchaw9xiPNcdxdO8bua/3q0BNfPZI3cRiatCstB H1aOfYmczK4p+pY3MErLAxAkkEUKQg1scTgCMFpEK+Roh0Eb4vOm7VRnhX6Z9lYLsxLMqWmPuUp y27PsIdCHaUEgTkfxnXg3EPqlC5Qu6AOuOs81GET+1u6ulyL5p9Xlm9KV6YaTzGg= X-Google-Smtp-Source: ABdhPJw0RJFyrFkK7ng+jsERmBVKHI5PtMqMrFdnDl16zcZCtjsaoeUX5oPL6ml0D3aDgc7WYiiU2zkeJ9IQ3w== X-Received: from chooglen.c.googlers.com ([fda3:e722:ac3:cc00:24:72f4:c0a8:26d9]) (user=chooglen job=sendgmr) by 2002:a17:902:9882:b0:13e:1749:daae with SMTP id s2-20020a170902988200b0013e1749daaemr2343207plp.60.1633393195354; Mon, 04 Oct 2021 17:19:55 -0700 (PDT) Date: Mon, 4 Oct 2021 17:19:31 -0700 In-Reply-To: <20211005001931.13932-1-chooglen@google.com> Message-Id: <20211005001931.13932-4-chooglen@google.com> Mime-Version: 1.0 References: <20210917225459.68086-1-chooglen@google.com> <20211005001931.13932-1-chooglen@google.com> X-Mailer: git-send-email 2.33.0.800.g4c38ced690-goog Subject: [PATCH v3 3/3] gc: perform incremental repack when implictly enabled From: Glen Choo To: git@vger.kernel.org Cc: Eric Sunshine , Taylor Blau , Glen Choo Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org builtin/gc.c has two ways of checking if multi-pack-index is enabled: - git_config_get_bool() in incremental_repack_auto_condition() - the_repository->settings.core_multi_pack_index in maintenance_task_incremental_repack() The two implementations have existed since the incremental-repack task was introduced in e841a79a13 (maintenance: add incremental-repack auto condition, 2020-09-25). These two values can diverge because prepare_repo_settings() enables the feature in the_repository->settings by default. In the case where core.multiPackIndex is not set in the config, the auto condition would fail, causing the incremental-repack task to not be run. Because we always want to consider the default values, we should always use the_repository->settings. Standardize on using the_repository->settings.core_multi_pack_index to check if multi-pack-index is enabled. Signed-off-by: Glen Choo --- builtin/gc.c | 5 ++--- t/t7900-maintenance.sh | 28 ++++++++++++++++++++++++---- 2 files changed, 26 insertions(+), 7 deletions(-) diff --git a/builtin/gc.c b/builtin/gc.c index f05d2f0a1a..070b7dccb1 100644 --- a/builtin/gc.c +++ b/builtin/gc.c @@ -1051,12 +1051,11 @@ static int maintenance_task_loose_objects(struct maintenance_run_opts *opts) static int incremental_repack_auto_condition(void) { struct packed_git *p; - int enabled; int incremental_repack_auto_limit = 10; int count = 0; - if (git_config_get_bool("core.multiPackIndex", &enabled) || - !enabled) + prepare_repo_settings(the_repository); + if (!the_repository->settings.core_multi_pack_index) return 0; git_config_get_int("maintenance.incremental-repack.auto", diff --git a/t/t7900-maintenance.sh b/t/t7900-maintenance.sh index 58f46c77e6..7b1b2581af 100755 --- a/t/t7900-maintenance.sh +++ b/t/t7900-maintenance.sh @@ -321,15 +321,15 @@ test_expect_success EXPENSIVE 'incremental-repack 2g limit' ' --no-progress --batch-size=2147483647 /dev/null && test_subcommand ! git multi-pack-index write --no-progress /dev/null && test_subcommand ! git multi-pack-index write --no-progress /dev/null && test_subcommand git multi-pack-index write --no-progress