-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neogit consistently throwing errors in specific repo (unable to pin point difference between working repo and this repo) #1486
Comments
I think I am having a similar issue here - that only happens on one of my repo as well. I had a look on the code based on my error and I think the issue is coming from the name of the repository open. Mine had a "%" symbol on it and after renaming the folder I was able to open Neogit without an issue. Can you maybe try renaming it @LarssonMartin1998 ? |
I'd be very curious if that's the issue, or if there's something else going on here. |
I just tried renaming it and it didn't have an effect. This was the original path to the root: /Users/martin.larsson/Projs/Repos/NameOfProject This is an enterprise repo so I changed the name of the repo in this comment but it has the exact same spacing and capitalization. Since this is an enterprise repo, it is on my work computer which has crowdstrike on it and the path is setup in CS to ignore some checks as to not impede our development (otherwise it drastically slows git and other things down). At first I thought that had something to do with it, but I moved the entire thing to ~/dev/git/nop and I still got the same issue |
Alright, could you grab some logs for me?
the logfile probably lives at |
Absolutely, here is the log:
|
I pushed some changes - could you pull the latest master and see if the issue persists, and if so.... more logs :) |
Hey, updated to latest and unfortunately the issue still persists, error log:
Neogit log:
|
So this is more of a hack than a fix, but I think if you set |
That works! I have some more findings from disabling that though. When I open Neogit, I get notifications in nvim-notify saying:
I should've mentioned in my issue post initally that my git is very slow due to crowdstrike. A regular git status takes ~2.5seconds. That might have something to do with it, and the reason it might fail in this project but not others is maybe because of the size of the repo. Thanks for your help on this. I really appreciate it. Do you want me to close the issue with this workaround, or should I keep it open? |
CKolkey, thanks for finding the setting to fix this. I have been having this issue for months, whenever the console opens it throws an error. I thought the console was opening because of the error, not the error being caused by the console. |
Ah, thats super annoying, sorry. It's been on my radar to fix, but my wife is about 8 months pregnant right now, so I haven't had tons of free time. But I kinda know whats up. |
Description
Hey,
I only get this issue in our specific repository at work where I am completely unable to use Neogit, it flat out doesnt' work. When I run the
:Neogit
command to open and interact with git, it doesn't load for a few seconds and saysv Head: 000000 (no commits)
. After a few seconds it throws an error log.Given the log, at first I thought it was some issue with the serialized session, however, clearing the session and disabling the auto_session plugin made no difference.
Unfortunately, I haven't been able to pin point what the difference is in this repo versus all other repos where this plugin works wonders.
Neovim version
NVIM v0.11.0-dev-604+g3b87fa406
Build type: Release
LuaJIT 2.1.1724512491
Operating system and version
macOS 14.6.1
Steps to reproduce
Difficult to reproduce unless you're in a git repo with this same issue which I am unable to pin point. Otherwise, start neovim, enter
:Neogit
, and observe the issue.Expected behavior
No response
Actual behavior
NeogitIssue.mp4
Here is the log:
Minimal config
The text was updated successfully, but these errors were encountered: