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:
signature.asc
Description: PGP signature
