Missing commit messages in history view

[matthesoundman]

I noticed lately in last few releases when I pull or fetch a large repo with a lot of commits some of the commit messages will not appear in the history view. If I highlight a row and view in the details all information is present. It seems like maybe some message buffer is not large enough in the viewer for the strings.

I know if I try to view in VSCode history viewer using Git Graph it works fine.

I am running Fork on Windows.

[DanPristupov]

Hi,

Do they appear after the application restart? Cab you send me the log file to support@fork.dev. The log is located at %localappdata%\fork\logs\fork.log

[DanPristupov]

On Windows it's in %localappdata%\fork\logs\fork.log

[matthesoundman]

Hi, after application restart they still do not appear.

I don't think I can share the log due to some information regarding the repo paths.

However, I can review it if you would kindly let me know what it is you are looking for in it.

Please let me know how I can help.

[DanPristupov]

You can redact any sensitive information. I'm mostly interested in errors.

[gSpidy]

Hi, i had the same issue, fork v1.94.1.0

Maybe it's somehow connected with recent git maintenance start activation in this repo (notice some missing prefetch refs, and then missing object)

First, I tried to disable git maintenance just in case, and then manually removed missing prefetch refs from .git folder, no luck. Missing refs errors were gone, but one about missing object remained and commit messages were still not visible.

Then i ran git gc --prune=now and it helped, commit messages reappeared

[DanPristupov]

@gSpidy thank you very much for sharing! 🤝

[fobin]

Hit the same. Did git maintenance stop and git gc --prune=now and got the messages back. Maybe someone else also has watched: https://www.youtube.com/watch?v=aolI_Rz0ZqY&t=1336s

[matthesoundman]

I tried the commands suggested and they do not work for me. I noticed after some time and then restart the PC and open Fork again the messages are all there.

The fact that the VSCode plugin Git Graph has no issue showing the commits tells me it is not related to the maintenance or prune.

I sent log to support@fork.dev.

[matthesoundman]

I haven't seen this issue for a while now. I think it is safe to close.

[Bombe]

This issue still occurs for me (macOS 13.6.7, Fork 2.43.1). The log file shows:

❌[BtResultExtensions.swift:33] > Bt error: Failed to read stashes in '/Users/bombe/Workspace/jFCPlib/.git': Cannot open object db '/Users/bombe/Workspace/jFCPlib/.git': Failed to open .idx file '/Users/bombe/Workspace/jFCPlib/.git/objects/pack/pack-33d9ee8860dd6eabcf1cfd98358e5d2c9ab4e546.idx': v1 .idx is not supported

So far, neither git gc (with --aggressive and/or --prune) nor git repack have been able to remedy the situation.