Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git-lfs has to be installed to clone or merge from repo #1089

Closed
huddlej opened this issue Apr 25, 2020 · 3 comments
Closed

git-lfs has to be installed to clone or merge from repo #1089

huddlej opened this issue Apr 25, 2020 · 3 comments
Labels
wontfix This issue does not need to be resolved

Comments

@huddlej
Copy link
Contributor

huddlej commented Apr 25, 2020

Current Behavior
When cloning the auspice repository (or trying to merge into an existing repo), I get the following error:

$ git clone https://github.com/nextstrain/auspice
Cloning into 'auspice'...
remote: Enumerating objects: 27630, done.
remote: Total 27630 (delta 0), reused 0 (delta 0), pack-reused 27630
Receiving objects: 100% (27630/27630), 13.95 MiB | 1.99 MiB/s, done.
Resolving deltas: 100% (20366/20366), done.
git-lfs smudge -- 'test/integration/__image_snapshots__/Color-by:author-snap.png': git-lfs: command not found
error: external filter git-lfs smudge -- %f failed -1
error: external filter git-lfs smudge -- %f failed
fatal: test/integration/__image_snapshots__/Color-by:author-snap.png: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'

Expected behavior

According to the DEV_DOCS, I should not need to have git-lfs installed unless I am running tests.

Possible solution

I think the .gitattributes file need to be modified somehow to prevent lfs from being required on clone/merge. If that isn't possible, it might be better to disable the LFS filter for now.

Environment

$ git --version
git version 2.10.0
@huddlej huddlej added bug Something isn't working high priority needs triage Needs triage by a Nextstrain team member labels Apr 25, 2020
@jameshadfield
Copy link
Member

jameshadfield commented Apr 26, 2020

Thanks for the detailed bug report here John. We can't have a situation where "git-lfs" is essential just to clone the repo. I was under the impression that this wouldn't happen -- without git-lfs installed the png files would simply be small text pointers rather than the actual file -- but this doesn't seem to be the case. Interestingly (confusingly), certain jobs in the GitHub CI checkout the repo without lfs and are working fine.

@eharkins (or anyone else), if you haven't already installed git-lfs could you see if you can reproduce this?

Also, @anescobar1991 do you have suggestions here?

@tsibley
Copy link
Member

tsibley commented Apr 27, 2020

I believe that git lfs is, correctly, not required. For example, I can clone the repo freshly without issue and without git lfs installed.

Looking more closely at the error message, I believe the issue is that the lfs filter, diff, and merge drivers are configured in @huddlej's git config but git lfs isn't actually installed anymore. e.g. a previous installation of git lfs was incompletely uninstalled.

@huddlej
Copy link
Contributor Author

huddlej commented Apr 27, 2020

@tsibley's conclusion is correct here. Removing my old LFS settings from .gitconfig fixed this problem. Thanks all and sorry for the false alarm!

@huddlej huddlej closed this as completed Apr 27, 2020
@huddlej huddlej added wontfix This issue does not need to be resolved and removed bug Something isn't working high priority needs triage Needs triage by a Nextstrain team member labels Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This issue does not need to be resolved
Projects
None yet
Development

No branches or pull requests

3 participants