From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Tim Walter (Visual Concepts)" <twalter@vcentertainment.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git hangs with --separate-git-dir
Date: Wed, 17 May 2023 01:20:19 +0000 [thread overview]
Message-ID: <ZGQr03G/9swNcHt0@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <BY5PR14MB36541924E1E6E5E912AFE0C2A5799@BY5PR14MB3654.namprd14.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3629 bytes --]
On 2023-05-16 at 21:55:35, Tim Walter (Visual Concepts) wrote:
> ---TAW--- The real issue is that it does a "very bad hang and mess up of the OS" if the repo is separate from the working directory.
> ---TAW--- In my case it happens to be a separate drive, not sure if that is relevant, I didn't try a separate folder on the same drive.
Git is an unprivileged process that doesn't install any sort of kernel
drivers. It should not have any sort of capability of hanging the OS.
If the OS is hanging, that's an OS or a driver bug.
> ---TAW--- It's not possible to uninstall the anti-virus SW, company policy and I don't have permissions for that level of configuration.
> ---TAW--- Our current solution (perforce) manages the same source files and does not have any interaction with the anti-virus
> ---TAW---We're careful to tell the anti-virus to ignore certain folders, and not to do on-demand scanning on those drives anyway.
> ---TAW--- That's one of the reasons we have separate drives (c: is protected a lot more than d: which is just the "work folders" for example.
I can tell you having answered a lot of Git-related questions on
StackOverflow and been on this list a long time, as well as being the
maintainer of Git LFS, that antiviruses often have weird behaviour just
being installed that breaks things randomly, even when fully
deactivated. For example, some antiviruses inject code into every
process, and that breaks lots of things by itself. Git is an
open source project and can't anticipate the behaviour of every
antivirus, so our semi-official policy has been that you should only use
the one shipped with the OS, if any.
It may be that Perforce happens to work here because it works
differently under the hood, but I simply can't say.
You could try running the command under the Windows Subsystem for Linux,
which often avoids antiviruses, and see if that fixes the problem for
you. It may work better and be faster as well. I like Debian for this
purpose, but Ubuntu is also very popular.
It may be that it's not antivirus-related at all, but the reason I asked
you to completely remove it and restart is to eliminate that problem,
since it's very frequently the cause, especially for random hangs. I
appreciate that that's difficult in a corporate environment, but I hope
you understand where we're coming from as well.
> ---TAW--- I expected that other people would have had this issue already, but it sounds like you've never heard of it, so maybe something odd
> ---TAW--- about our particular configuration? But I don't know what, except that:
> ---TAW--- : it's a large project
> ---TAW--- : it contains binary as well as text files
> ---TAW--- : I am trying to use 2 different local drives
> ---TAW--- : I am using windows, sorry can't help that, we are forced to develop using windows tools.
I haven't seen this problem, since I only use Windows extremely
occasionally for testing a few things. I'm unable to reproduce any sort
of problem using a separate Git dir on a separate filesystem on Linux.
You can try reporting it to the Git for Windows issue tracker at
https://github.com/git-for-windows/git/issues, and maybe they can help
you, but I'm pretty sure this is not a bug in Git itself. Git for
Windows ships a lot of code besides Git itself, and it's possible that
something there is related, though, and they'll have the knowledge to
help out more. You can try searching the issue tracker to see if
somebody has reported a similar problem before.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2023-05-17 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:54 git hangs with --separate-git-dir Tim Walter (Visual Concepts)
2023-05-16 21:30 ` brian m. carlson
2023-05-16 21:55 ` Tim Walter (Visual Concepts)
2023-05-17 1:20 ` brian m. carlson [this message]
2023-05-17 7:11 ` Erik Cervin Edin
2023-05-17 16:31 ` Tim Walter (Visual Concepts)
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=ZGQr03G/9swNcHt0@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=twalter@vcentertainment.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).