You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using netlify lfs for a repository but was suddenly unable to retrieve the files via git lfs fetch.
A complete re-install of the netlify-cli and the credential helper as well as a fresh clone of the repository (and running netlify lm:install) dit not help, unfortunately.
netlify status confirms that the local repository is connected to the netlify site.
netlify lm:info returns:
✔ Checking Git version [2.23.0]
✔ Checking Git LFS version [2.8.0]
✔ Checking Git LFS filters
✔ Checking Netlify's Git Credentials version [0.1.8]
When I run DEBUG=1 git lfs fetch, it seems like the process is stuck in a loop. Starting with
However it then immediately starts with initializing the credential helper again (as in the lines above) — and continues being stuck in this loop. Are the credentials not properly stored or how could I go about finding a solution for this issue?
I'm running macOS 10.14.6 (18G95) with node v10.16.3.
The text was updated successfully, but these errors were encountered:
I'm using netlify lfs for a repository but was suddenly unable to retrieve the files via
git lfs fetch
.A complete re-install of the netlify-cli and the credential helper as well as a fresh clone of the repository (and running
netlify lm:install
) dit not help, unfortunately.netlify status
confirms that the local repository is connected to the netlify site.netlify lm:info
returns:When I run
DEBUG=1 git lfs fetch
, it seems like the process is stuck in a loop. Starting withit then gets a json response containing data about the site and outputs
However it then immediately starts with initializing the credential helper again (as in the lines above) — and continues being stuck in this loop. Are the credentials not properly stored or how could I go about finding a solution for this issue?
I'm running macOS 10.14.6 (18G95) with node v10.16.3.
The text was updated successfully, but these errors were encountered: