Open finnless opened 1 year ago
Great detective work!
In general, your accounts have limited resources allocated to them (to ensure that you don't accidentally mess up other accounts), and that is the cause of this. Another fix (which will work with some other commands as well) is to add the -j1
flag to the end of your git clone
command.
Again, we'll discuss more of this on Monday.
When I run this command
it throws the following error on lambda server:
I reproduced the same error on @abizermamnoon account.
I was able to resolve the issue by making the following git config change:
Credit to this Stack Overflow post for the fix.
Hopefully this helps others if they run into the same issue.