Menu
I'm deploying to CircleCI and but my code is timing out.
The command in particular that CircleCI is calling that's causing the time-out is during the checkout stage:
git reset --hard SHA
Where SHA is the hash of the build, but upon ssh'ing in I noted that HEAD and others that I tried also run forever.
At that point the code has been checked out with:
git clone --quiet [email protected]:Organization/Repo.git . --config core.compression=9 --depth 10 --no-single-branch
Why would git reset --hard run (seemingly) forever on the CircleCI environment, and what fixes are reasonably available?
More details (we've got some git-lfs files here, too):
EDIT This appears related to:
I would also note that adding GIT_LFS_SKIP_SMUDGE=1 (in the CircleCI Project config) has not had any useful effect.
It does help to go back to Ubuntu 12, but obviously that's less than ideal.
EDIT
Here's a recent bug report I filed: https://discuss.circleci.com/t/cannot-pull-with-git-lfs/14346
(Just to ensure visibility, because my other reports were buried in comments)
764
We can use the command git fsck to recover the files after a hard reset.
git reset --hard. Reset the staging area and the working directory to match the most recent commit. In addition to unstaging changes, the --hard flag tells Git to overwrite all changes in the working directory, too.
3.0. 2 (28 Oct 2021) This release is a bugfix release which fixes a variety of problems seen since 3.0. 0, including problems with empty files, git lfs fsck --pointers , and the testsuite.
The issue was a typo, namely that CircleCI was running version 1.0, but should have been using 2.0.
In particular, I had created a .circleci/config.yaml, with the appropriate config.
... however, it should've been called .circleci/config.yml.
76
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
