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
Lazygit hangs terminal on listing commits #3529
Comments
I don't suppose you can share that repo? |
I'm afraid not, unfortunately. |
Ok, then it's going to be a bit more cumbersome to figure this out... My suspicion is that it has something to do with the git log command that lazygit issues to load the commits. I don't see this in the log that you posted; look for a line that has |
I don't see any lines starting with Errors:
Not sure why it is trying to reach out for Full log:
|
The errors that you see in the log are normal, nothing to worry about. And no, you don't need a The reason why you don't see the git log command seems to be because we only log it once it has completed, so from that I can only conclude that this command hangs for some reason. Can you try running this in the terminal:
|
Ok, so I think I found the issue thanks to the command above. First, I have
Using unaliased Proper commit list revealed, that in one commit, when converting
When I rebased the branch and removed the problematic commit, it started working. However, I'm not sure I can force push to that repo. Strange that no other git tool / command finds that output problematic. Maybe there is a way to escape the commit descriptions in lazygit? Also maybe a good idea to figure out the actual unaliased |
We are not actually using I'm not sure I understand the problem yet. You are talking about the description field, but the diff output you pasted only shows the diff, not the description, which doesn't seem to be relevant here. Could you paste the output of
|
Ooh, sure, didn't get that, sorry.
This is the commit description (the whole diff) :) The output of the command:
And it goes for plethora of lines. |
I can reproduce it here, it happens whenever you have a commit whose subject is longer than about 65535 characters (a bit less than that, but that's details). Here's a fix: #3533. Can you build from source and try it? |
Whoa, that was fast. It works like a charm :). Thanks for the (lightning fast) help, really appreciate it! |
Describe the bug
I have a weird issue that Lazygit does not list the commits in the
[4] Commits
window (but it lists them in theLog
graph window on the right hand side - see screenshot below). Moreover, when trying to do any operation on that branch, like trying to checkout different branch or list the commits by using in[3] Local branches
view, the terminal hangs (in a way it has to be killed entirely).The weird thing about this is that it is happening only in one particular repository on one particular branch (and any branches created from it). It doesn't happen for the same repo with a branch not derived from the
develop
(the problematic branch).It started somewhat after updating lazygit from 0.40.x but I tried downgrading to 0.40.2 and the same happens. At this point I'm clueless and desperate as it really messed up my workflow.. Please help, any ideas are appreciated.
Testing
I tried to
git fsck
(no errors)lazygit --debug
manually in the terminal. Nothing seems to return any error or hang the terminalBelow is the debug log output from starting
lazygit
to issuing on[3] Local branches
, which hangs the terminal:To Reproduce
No clue how to reproduce that as it happens only on one branch on particular repository
Expected behavior
Commits are listed properly in
Commit
window, Lazygit does not hang the terminal when trying to enter branch commits or checkout another branchScreenshots
Version info:
commit=aa81e191e2905e6959f1d8e51c8589764ca0c520, build date=2024-04-25T06:53:14Z, build source=unknown, version=aa81e191, os=linux, arch=amd64, git version=2.43.2
Ubuntu 22.04 on WSL2
The text was updated successfully, but these errors were encountered: