Git lfs configuration for lsst

Support
#1

Hi, I’m trying to configure Git LFS for downloading LSST data packages following https://pipelines.lsst.io/install/git-lfs.html. I have modified my .gitconfig and .git-credentials files, but I still receive this error when I clone the testdata_decam Git repository:

Cloning into ‘testdata_decam’…
remote: Enumerating objects: 43, done.
remote: Counting objects: 100% (43/43), done.
remote: Compressing objects: 100% (40/40), done.
Receiving objects: 92% (1144/1243)sed 8 (delta 3), pack-reused 1200
Receiving objects: 100% (1243/1243), 159.50 KiB | 1.27 MiB/s, done.
Resolving deltas: 100% (213/213), done.
error: invalid path ‘rawData/cpCalib/defects/1970-01-01T00:00:00/defects-1970-01-01T00:00:00-001.fits’
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with ‘git status’
and retry with ‘git restore --source=HEAD :/’

It seems that I haven’t properly set up git-lfs. This is my modified .gitconfig file according to the information in the turorial.
Did I miss something?

[diff “astextplain”]
textconv = astextplain
[filter “lfs”]
clean = git-lfs clean – %f
smudge = git-lfs smudge – %f
process = git-lfs filter-process
required = true
[http]
sslBackend = openssl
sslCAInfo = C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
[core]
autocrlf = true
fscache = true
symlinks = false
[credential]
helper = manager
#Cache anonymous access to DM Git LFS S3 servers
[credential “https://lsst-sqre-prod-git-lfs.s3-us-west-2.amazonaws.com”]
helper = store
[credential “https://s3.lsst.codes”]
helper = store

#2

At a guess:

Given the reference to C:/Program Files/..., I imagine you’re running Windows. The colon (:) is a reserved character in filenames on Windows. The path including 1970-01-01T00:00:00 is therefore being rejected as invalid.

I’m not very familiar with Windows, and I don’t have a convenient system to hand (at least, not one with Git LFS etc installed on it), so I can’t check for sure.

If I’m right, be aware that we don’t build or test our code on Windows; it’s not really surprising that it doesn’t work. You might have more luck installing in a Linux VM.

#3

Thank you for the answer. I think your guess is right, I’ll try with a Linux VM.