If you use DM’s Git LFS, please take a moment to check that your Git LFS client is version 2.3.4 or newer.
You can check the version of your Git LFS client by running:
git-lfs version
You can get a new Git LFS client from https://git-lfs.github.com or through your package manager (for example, brew upgrade git-lfs if you’ve installed Git LFS through Homebrew).
We’ve recently observed instances where extra credentials for S3 endpoints need to be cached when using very old clients (<2.0). We don’t know why this started happening since our Git LFS server hasn’t changed recently. We also think it may be a Mac-specific issue. We do know that a modern git-lfs client does not have the issue. We’ve adopted git-lfs version 2.3.4 as the minimum required version because that is the version deployed with lsstsw in our continuous integration environments.
If Git LFS is currently working for you, you can likely keep using it (no need to immediately rebuild your lsstsw installation). But if Git LFS suddenly breaks, upgrading the client is the best way we’ve found to fix that issue.
Mine was failing due to being out of date (version 1.5.5). However, rebuilding lsstsw isn’t enough to cause lsstsw/lfs/bin to be updated. I think you have to re-run bin/deploy for that to happen.