git push --progress -v
Pushing to firstname.lastname@example.org:XXX/XXX.git
Counting objects: ###, done.
Delta compression using up to 16 threads.
fatal: unable to create thread: Resource temporarily unavailable
error: pack-objects died with strange error
error: failed to push some refs to 'email@example.com:XXX/XXX.git'
What I had read suggested that this is something that can only be alleviated at the server side (and I'm using a hosted bitbucket.org Git repo). Note, this may be following a fairly substantial git commit containing 100s of files of modifications and deletions during a botched Drupal contrib modules update....
Smart man Marcus Bertrand [Atlassian] correctly pointed out that this was actually a local client (well, remote dev where I'm git-commit'ing) configuration issue. I was unable to crack the specific config to push it through (ha, get it?) but this clever workaround DID do the trick for me:
To confirm all was made aright again, I made a quick git commit, git push (voila!), git pull, git goin' goin', git gone!
Bronius, you can see you did in fact answer your question in the same breath with which you had asked it. To this, I dub thee a darn fool and community advocate.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot