One of the team's developers are having problems pulling down the git lfs content from a bitbucket repository after cloning the repository.
The repository is accessed via the https protocol along with app password. The repository is able to successfully cloned however all of the assets marked to be tracked by git lfs are marked as changed.
If we try to discard the changes, we get the following response from git.
batch response: Repository or object not found: https://bitbucket.org/companyname/repo-name/src/master.git/info/lfs/objects/batch
Check that it exists and that you have proper access to it
error: failed to fetch some objects from 'https://bitbucket.org/companyname/repo-name/src/master.git/info/lfs'
From reading that message, it appears to be an authentication issue but if there was a successful clone of the main repository, you'd think the authentication would also be valid for the lfs content.
When inspecting these assets, the change to the files resembles that of an asset deletion.
This issue is only affecting one member in the team and other team members have no problems pulling down the lfs tracked assets. This member also in the same user groups on bitbucket for access to repositories and permissions.
We tried duplicating the project and uploading a new copy of the repository to bitbucket and the same issue occurs when they clone the repository.
The final confusing part, the user has been able to successfully clone other repositories with lfs tracked assets and have no problems pulling down these assets.
If the user is having issues fetching lfs content over HTTPS, I would suggest that they first ensure that the remote URL has been updated to include the App Password to avoid any potential authentication issues:
git remote set-url origin https://USERNAME:APP_PASSWORD@bitbucket.org/companyname/repo-name.git
If the clone command is using the App Password, but their remote URL is not updated - this would explain why they are able to clone but not able to pull.
Once this is done, I would suggest having them also ensure that git lfs is definitely installed on their local repository by running the following command, as if it is not - any git lfs commands will not work as GIT will not understand how to pull the data:
git lfs install
Once the above steps have been performed, ask them to try to perform the git lfs fetch without the lfs path included - as this is not required and can cause issues when trying to locate the remote repo location:
git lfs fetch origin main
Hope this helps, let me know if there are any issues.
- Ben (Bitbucket Cloud Support)
We found that we were missing the username in the git path.
The path we had that was causing the problem.
The path we used that resolved the problem
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events