Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,920
Community Members
 
Community Events
184
Community Groups

git push fail with "error: remote unpack failed: eof before pack header was fully read..."

Edited

Hi!

 

I have at least two repositories that I currently fail to do git push to. Both fail with the error:

error: remote unpack failed: eof before pack header was fully read
To bitbucket.org:da9l/<redacted repo>.git
! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'bitbucket.org:da9l/<redacted repo>.git'

 

What am I missing here?

1 answer

0 votes
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 24, 2022

Hello @da9l ,

Welcome to Atlassian Community.

The repack error might happen if you run out of memory when compressing large files.

Would you please try executing the below commands to limit the pack memory and threads,  and try again ?

git config --global pack.windowMemory "100m"
git config --global pack.packSizeLimit "100m"
git config --global pack.threads "1"

Reference: https://stackoverflow.com/a/66246671

Also, you can make a consistency check in your repo to confirm there are no corrupted files:

git fsck

Once you execute the commands above, you can try pushing to the repository again and check how it goes.

Hope that helps, let us know in case you run into any issues.

Thank you, @da9l .

Kind regards,

Patrik S

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events