From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Hecker, David A" <David.Hecker@conduent.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Potential Bug - GIT/GIT LFS doing dnsquery on an IP address
Date: Mon, 21 Mar 2022 23:51:04 +0000 [thread overview]
Message-ID: <YjkPaBzrTeiskVTv@camp.crustytoothpaste.net> (raw)
In-Reply-To: <BN8PR20MB28354228F53ACD3680F505E6FB169@BN8PR20MB2835.namprd20.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3102 bytes --]
Hey,
On 2022-03-21 at 23:20:25, Hecker, David A wrote:
> I started the message below with git bugreport so I think I have all the details. (UPPERCASE to highlight; not shouting. 😊)
>
> Thanks!
> --Dave Hecker
>
>
> ====================================================================================================
> WHAT DID YOU DO BEFORE THE BUG HAPPENED? (STEPS TO REPRODUCE YOUR ISSUE)
> ----------------------------------------------------------------------------------------------------
> I have an older laptop running Visual Studio 2019 and Git-2.35.1.2-64-bit.exe WITH the "GIT LFS" option checked, which is working as expected: committing a change to a large file and pushing the changes DOES update the remote repository with the change, and other team members who ALREADY HAVE A FULL COPY OF THE OLDER LARGE FILE are able to pull changes and will receive the updated copy of that file.
>
> Another team member and I got a new laptop and set up Visual Studio 2019 and Git-2.35.1.2-64-bit.exe, and then attempted to clone the repository. The clone succeeds, but checkout fails with this error:
>
> batch response: Post https://tfs.acsgs.com/tfs/PDSI/HRS2/Learning/_git/KnowledgeConnection.git/info/lfs/objects/batch:
> lookup 216.115.169.22: dnsquery: DNS name does not exist.
>
> GIT/GIT LFS successfully resolved "tfs.acsgs.com" to the IP 216.115.169.22 for the clone, but then it seems like it’s mistakenly attempted a DNS lookup of "216.115.169.22" which fails because it's already an IP address, NOT a DNS name. (Doing "nslookup 216.115.169.22" fails in a similar/expected way: "can't find 216.115.169.22: Non-existent domain".)
>
> IMPORTANT: I then tried cloning to a new folder on my OLDER (Windows 7) laptop, and GOT THE SAME ERROR. Therefore I SUSPECT this is NOT related to my NEWER (Windows 10) vs. OLDER (Windows 7) laptop, but instead seems to be a GIT/GIT LFS bug…and only when attempting the initial download of an “actual” file.
>
> Another possibility is our internal TFS server perhaps has changed configuration since the first time we cloned our repository, but it seems unlikely (I can manually download a large file into my local folder, then GIT/GIT LFS will manage it properly…it seems to be only when trying to make the initial download of a full file that fails with this “lookup 216.115.169.22: dnsquery: DNS name does not exist” error).
> ====================================================================================================
This looks like a Git LFS issue, and Git LFS is managed independently
from this project. Could you please open an issue on the Git LFS issue
tracker[0] instead, including all of this information, filling out the
issue template, and including the output when using GIT_TRACE=1
GIT_TRANSFER_TRACE=1 GIT_CURL_VERBOSE=1 (stripping out any
authentication headers)?
That would allow one of us who work on Git LFS to look at this in more
detail.
Thanks.
[0] https://github.com/git-lfs/git-lfs
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2022-03-21 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 23:20 Potential Bug - GIT/GIT LFS doing dnsquery on an IP address Hecker, David A
2022-03-21 23:51 ` brian m. carlson [this message]
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=YjkPaBzrTeiskVTv@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=David.Hecker@conduent.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).