git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victoria Dye <vdye@github.com>
To: fawaz ahmed0 <fawazahmed0@hotmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: "reject arguments in cone-mode that look like patterns" doesn't work in macos-12
Date: Thu, 14 Jul 2022 12:47:34 -0700	[thread overview]
Message-ID: <a1580785-e35c-9a2d-7fa1-c3d7fc62883b@github.com> (raw)
In-Reply-To: <BL0PR13MB427538CEAD5481CCBF6D195DF1889@BL0PR13MB4275.namprd13.prod.outlook.com>

fawaz ahmed0 wrote:

Hi Fawaz,

Please make sure you "Reply-all" to include the mailing list in the
discussion, and make sure to inline or bottom-post your replies.

> I assume it's v2.37, you can reproduce it on github actions macos 12.

Per the virtual environment specification [1] linked in the runner execution
[2], the Git version used on these agents is 2.36.1. 

[1] https://github.com/actions/virtual-environments/blob/macOS-12/20220627.3/images/macos/macos-12-Readme.md
[2] https://github.com/fawazahmed0/currency-api/runs/7312663698?check_suite_focus=true#step:1:11

> 
> My github actions workflow didn't fail, even when I was setting pattern in cone mode.
> 
> please see: https://github.com/fawazahmed0/currency-api/actions/runs/2660320076/workflow#L31

Based on the commands you linked, combined with the fact that cone mode was
not made the default until v2.37, you're setting a wildcard pattern in *non*
cone mode. If you want to use cone mode in version v2.36, try running 'git
sparse-checkout reapply --cone' after your clone to set the appropriate
config.

> 
> 
> 
> 
> From: Victoria Dye <vdye@github.com>
> Sent: Friday, July 15, 2022 12:48 AM
> To: fawaz ahmed0 <fawazahmed0@hotmail.com>; git@vger.kernel.org <git@vger.kernel.org>
> Subject: Re: "reject arguments in cone-mode that look like patterns" doesn't work in macos-12 
>  
> fawaz ahmed0 wrote:
>> Please refer: https://github.com/git/git/commit/8dd7c4739bded62175bea1f7518d993b39b51f90#commitcomment-78433458
>>
>>
>> Using patterns in cone mode should fail, but it doesn't seem to fail on macOS-12(github actions)
> 
> Can you confirm which version is being used on that MacOS agent? For
> example, you could add a call to 'git version' in the workflow and see what
> it prints out. I suspect that the agent may be using an older version of
> Git, which would mean that the sparse-checkout is initialized in *non* cone
> mode.
> 
> For what it's worth, my local development machine is also MacOS 12 (running
> Git v2.37), and I'm correctly seeing the error in a cone mode
> sparse-checkout.
> 
>>
>> Step to reproduce(try in macOS-12):
>>
>> git clone --filter=blob:none --no-checkout --depth 1 --sparse https://github.com/fawazahmed0/currency-api.git . 
>> git sparse-checkout add 'latest/*'
>>
>> Thanks
>> Fawaz Ahmed


  parent reply	other threads:[~2022-07-14 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BL0PR13MB42750BC5C4837B7B0BD1885EF1889@BL0PR13MB4275.namprd13.prod.outlook.com>
2022-07-14  8:00 ` "reject arguments in cone-mode that look like patterns" doesn't work in macos-12 fawaz ahmed0
2022-07-14 19:18   ` Victoria Dye
     [not found]     ` <BL0PR13MB427538CEAD5481CCBF6D195DF1889@BL0PR13MB4275.namprd13.prod.outlook.com>
2022-07-14 19:47       ` Victoria Dye [this message]
2022-07-14 20:05         ` fawaz ahmed0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a1580785-e35c-9a2d-7fa1-c3d7fc62883b@github.com \
    --to=vdye@github.com \
    --cc=fawazahmed0@hotmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).