I've been battling with the sendback error for days

[researchsecurity]

Select Topic Area

Bug

Body

I've been battling with the sendback error for days. I have a heavy file project but I am doing malware research so one would expect such. The steps I have tried are here, but it appears I am doomed and have been for days in trying to manage my files and move directories.

06:02:29.837900 git.c:463               trace: built-in: git push
06:02:29.838891 run-command.c:659       trace: run_command: unset GIT_PREFIX; ssh git@github.com 'git-receive-pack '\''researchsecurity/malware.git'\'''
06:02:30.645703 pkt-line.c:85           packet:         push< 9939d2df3e69a8313cbd3e15ee5e58b3999f0247 refs/heads/trunk\0report-status report-status-v2 delete-refs side-band-64k ofs-delta atomic object-format=sha1 quiet agent=github/spokes-receive-pack-2348e814e9289a5a43149ee09a71f20097895cf8 session-id=4b66a6cf91060eadf6f22280b89d7e6e push-options
06:02:30.645768 pkt-line.c:85           packet:         push< 0000
06:02:30.647240 pkt-line.c:85           packet:         push> 9939d2df3e69a8313cbd3e15ee5e58b3999f0247 b6af24f521b8c93092b81c9d0770c246507629e4 refs/heads/trunk\0 report-status-v2 side-band-64k object-format=sha1 agent=git/2.42.0
06:02:30.647259 pkt-line.c:85           packet:         push> 0000
06:02:30.647317 run-command.c:659       trace: run_command: git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress
06:02:30.662152 git.c:463               trace: built-in: git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress
Enumerating objects: 1938, done.
Counting objects: 100% (1938/1938), done.
Delta compression using up to 4 threads
Compressing objects: 100% (804/804), done.
send-pack: unexpected disconnect while reading sideband packet
Connection to github.com closed by remote host.
fatal: the remote end hung up unexpectedly

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐