From: Jesse Kasky <jkasky@slack-corp.com>
To: git@vger.kernel.org
Subject: BUG: config.c:129: kvi should not be set while parsing a config source
Date: Wed, 21 Jun 2023 16:45:44 -0700 [thread overview]
Message-ID: <CAJSLrw6qhHj8Kxrqhp7xN=imTHgg79QB9Fxa9XpdZYFnBKhkvA@mail.gmail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
git clone --no-checkout --sparse --filter=blob:none --depth=1 <repo> <dir>
cd <dir>
git sparse-checkout add <dir1> <dir2>
git fetch --depth=1 origin <commit>
What did you expect to happen? (Expected behavior)
Expected the fetch to complete
What happened instead? (Actual behavior)
Received the following error:
BUG: config.c:129: kvi should not be set while parsing a config source
[1] 5842 abort /opt/homebrew/bin/git fetch --depth=1 origin
What's different between what you expected and what actually happened?
Did not expect to encounter an abort.
Anything else you want to add:
Two items I came across while trying to troubleshoot:
https://github.com/git/git/commit/9828453ff00b330c57daa3a8b672cbb5f0cdce34
https://github.com/Homebrew/homebrew-cask-fonts/issues/7718
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.41.0
cpu: arm64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Darwin 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:24
PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000 arm64
compiler info: clang: 14.0.3 (clang-1403.0.22.14.1)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks]
next reply other threads:[~2023-06-21 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 23:45 Jesse Kasky [this message]
2023-06-23 13:36 ` BUG: config.c:129: kvi should not be set while parsing a config source Derrick Stolee
2023-06-23 19:22 ` Glen Choo
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJSLrw6qhHj8Kxrqhp7xN=imTHgg79QB9Fxa9XpdZYFnBKhkvA@mail.gmail.com' \
--to=jkasky@slack-corp.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).