{"id":1499,"date":"2024-01-28T12:37:54","date_gmt":"2024-01-28T03:37:54","guid":{"rendered":"https:\/\/dohokin.com\/?p=1499"},"modified":"2024-01-28T19:30:13","modified_gmt":"2024-01-28T10:30:13","slug":"unable-to-push-a-commit-due-to-missing-lfs-objects-after-using-laravel-shift-to-upgrade-application-from-5-8-to-6-x","status":"publish","type":"post","link":"https:\/\/dohokin.com\/?p=1499","title":{"rendered":"Unable to push a commit due to missing LFS objects after using Laravel Shift to upgrade application from 5.8 to 6.x"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Dealing with Git LFS (Large File Storage) issues can be tricky, especially after a significant upgrade like moving a Laravel application from 5.8 to 6.x. Your issue seems to be with Git LFS not properly tracking or finding the necessary files in the LFS storage. Let’s go through the steps to troubleshoot and resolve this issue:<\/p>\n\n\n\n

Step 1: Verify Git LFS Installation<\/h3>\n\n\n\n

First, ensure that Git LFS is correctly installed on your system. Run:<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
git<\/span> <\/span>lfs<\/span> <\/span>install<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
This command will set up any necessary hooks in your Git configuration.<\/p>\n\n\n\n
Step 2: Check LFS Tracking<\/h3>\n\n\n\n
Check if the mentioned files are being tracked by Git LFS:<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
git<\/span> <\/span>lfs<\/span> <\/span>ls-files<\/span><\/span>\n<\/span><\/code><\/pre><\/div>\n\n\n\n
This command lists all files currently being tracked by Git LFS. If the files in question (sample.pdf<\/code> and sample2.pdf<\/code>) aren’t listed, they aren’t being tracked.<\/p>\n\n\n\n
Step 3: Track Missing Files<\/h3>\n\n\n\n
If the files aren’t being tracked, you can manually track them:<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
git<\/span> <\/span>lfs<\/span> <\/span>track<\/span> <\/span>"<\/span>vendor\/srmklive\/paypal\/tests\/Mocks\/samples\/sample.pdf<\/span>"<\/span><\/span>\ngit<\/span> <\/span>lfs<\/span> <\/span>track<\/span> <\/span>"<\/span>vendor\/srmklive\/paypal\/tests\/Mocks\/samples\/sample2.pdf<\/span>"<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
Then add and commit the .gitattributes<\/code> file which is updated by the track<\/code> command:<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
git<\/span> <\/span>add<\/span> <\/span>.gitattributes<\/span><\/span>\ngit<\/span> <\/span>commit<\/span> <\/span>-m<\/span> <\/span>"<\/span>Track LFS files<\/span>"<\/span><\/span>\n<\/span><\/code><\/pre><\/div>\n\n\n\n
Step 4: Re-Add Files to LFS<\/h3>\n\n\n\n
Re-add the files to ensure they are correctly referenced in LFS:<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
git<\/span> <\/span>add<\/span> <\/span>vendor\/srmklive\/paypal\/tests\/Mocks\/samples\/sample.pdf<\/span><\/span>\ngit<\/span> <\/span>add<\/span> <\/span>vendor\/srmklive\/paypal\/tests\/Mocks\/samples\/sample2.pdf<\/span><\/span>\ngit<\/span> <\/span>commit<\/span> <\/span>-m<\/span> <\/span>"<\/span>Re-add LFS files<\/span>"<\/span><\/span>\n<\/span><\/code><\/pre><\/div>\n\n\n\n
Step 5: Push Changes<\/h3>\n\n\n\n
Attempt to push your changes again:<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
git<\/span> <\/span>push<\/span><\/span>\n<\/span><\/code><\/pre><\/div>\n\n\n\n
Step 6: Check for .gitignore Conflicts<\/h3>\n\n\n\n
Ensure that .gitignore<\/code> isn’t causing the files to be overlooked. Files listed in .gitignore<\/code> won’t be tracked by Git or Git LFS.<\/p>\n\n\n\n
Step 7: Inspect LFS Storage<\/h3>\n\n\n\n
If the issue persists, the problem might be on the server-side with LFS storage. Check the configuration of your Git repository host for any LFS limitations or issues.<\/p>\n\n\n\n
Step 8: Contact Support<\/h3>\n\n\n\n
If you’re still facing issues, it might be helpful to contact the support team of your Git repository hosting service (like GitHub, GitLab, etc.) for assistance, as they might have more insights into LFS-related issues on their platforms.<\/p>\n\n\n\n
Additional Notes:<\/h3>\n\n\n\n
    \n
  • Commit Size<\/strong>: Be aware of the size of the files you’re committing with LFS, as there might be size limits depending on your Git hosting service.<\/li>\n\n\n\n
  • LFS Quotas<\/strong>: Some services have quotas on LFS usage; exceeding these can cause issues.<\/li>\n\n\n\n
  • Network Issues<\/strong>: Sometimes, LFS problems are related to network issues or specific configurations required by your Git repository host.<\/li>\n<\/ul>\n\n\n\n
    Remember, using lfs.allowincompletepush<\/code> as a workaround is not recommended as it can lead to an incomplete history and potential issues with your repository’s integrity. It’s better to resolve the root cause of the missing LFS objects.<\/p>\n\n\n
    Tell me more step by step about Unable to push a commit due to missing LFS objects, after having utilized laravel shift to upgrade application to 6.x from 5.8<\/p>\n
    As the title suggests, I attempted a laravel shift on my project to go to 6.x from 5.8. I followed the changelog provided by the laravel shift branch in my project and made appropriate changes, and when I tried to commit and push changes, I received an error indicating that certain LFS upload objects were missing.<\/p>\n
    Error:
    (missing) vendor\/srmklive\/paypal\/tests\/Mocks\/samples\/sample.pdf
    (missing) vendor\/srmklive\/paypal\/tests\/Mocks\/samples\/sample2.pdf<\/p>\n
    However, when I checked the file path, the files are present and not missing or hidden.<\/p>\n
    Having received this error, I tried to fix it by running the git command to allow incomplete push.<\/p>\n
    git config lfs.allowincompletepush true\n<\/code><\/pre>\n
    However, this did not fix my problem and I still received an error indicating that the files are missing.<\/p<\/p>\n
    Unable to push a commit due to missing LFS objects after using Laravel Shift to upgrade application from 5.8 to 6.x<\/h1>\n
    After attempting a Laravel shift on the project to upgrade from version 5.8 to 6.x, an error occurred while trying to commit and push changes due to missing LFS (Large File Storage) objects. Specifically, it reported that certain LFS upload objects were missing, such as ‘sample.pdf’ and ‘sample2.pdf’ within the ‘vendor\/srmklive\/paypal\/tests\/Mocks\/samples’ path. Although the files were present and not hidden, the error persisted. In an attempt to resolve the issue, the command ‘git config lfs.allowincompletepush true’ was executed, but this did not resolve the problem and the files were still reported as missing. Additional troubleshooting steps may be necessary to resolve this issue.<\/p>\n
    Keyword 1: Laravel Shift, Keyword 2: LFS (Large File Storage)<\/h1>\n
    Keyword 1 Explained: Laravel Shift is a service that automates the process of upgrading Laravel applications to newer versions by analyzing the codebase and making the necessary changes to the code and configuration files.
    Keyword 2 Explained: LFS, or Large File Storage, is a Git extension that supports storing large files separately from the Git repository, and it helps manage large binary files efficiently.<\/p>\n
    Upgrade Your Laravel Application Smoothly<\/h1>\n
    Don’t let LFS issues hold back your Laravel upgrade. Learn how Laravel Shift and LFS can impact your development process and find solutions to tackle these challenges effectively.<\/p>","protected":false},"excerpt":{"rendered":"
    Unable to push a commit <\/p>\n","protected":false},"author":2,"featured_media":1514,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1],"tags":[80,81],"_links":{"self":[{"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/posts\/1499"}],"collection":[{"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dohokin.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1499"}],"version-history":[{"count":2,"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/posts\/1499\/revisions"}],"predecessor-version":[{"id":1515,"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/posts\/1499\/revisions\/1515"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dohokin.com\/index.php?rest_route=\/wp\/v2\/media\/1514"}],"wp:attachment":[{"href":"https:\/\/dohokin.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1499"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dohokin.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1499"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dohokin.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1499"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}