Issue Summary

git pull/fetch/clone operation via HTTPS sometimes still shows older commits. Newer commits on the remote are not shown in the repository.

Steps to Reproduce

1. git clone/pull via HTTPS

Expected Results

It is expected that all the commits that are in the repository are pulled to the local copy of the repository(clone/pull)

Actual Results

Older commits are shown

Workaround

One of the 3 workarounds mentioned below resolves the issue.

1. Performing git operations over SSH helps.
2. Push a new commit to remote and try to pull/clone again.
3. Alternatively, triggering GC on the repository solves the issue.

Update Thu 08, Aug 2024

We have rolled out several improvements to alleviate this problem. We enabled support for git v2 protocol and added optimization to how we use certain caches that were responsible for service stale refs. These improvements collectively help eliminate the root cause behind the symptoms reported here so we are marking this ticket as closed.