Summary: As of June 30th 2023 we are aware of an issue that is causing errors when running brew update. The problem has been identified as repository corruption on the GitHub side, and GitHub has taken steps to fix it. See cloning repo is broken · Issue #135315 · Homebrew/homebrew-core · GitHub for details of this issue. On the same day the issue was resolved but on July 3rd 2023 some user notice the similar issue resurfacing. brew update nonzero return value · Homebrew · Discussion #4612 · GitHub
Issue Description:
Users have reported encountering the following error when running brew update:
> brew update
error: Could not read 623226b77a148708197a10c0d1eab3f8d6ca005b
fatal: revision walk setup failed
error: https://github.com/Homebrew/homebrew-core did not send all necessary objects
Impact:
This issue has affected users of Homebrew, a popular package manager for macOS, as well as CircleCI users who calls brew update for their CI/CD workflows. The error occurs due to repository corruption on the GitHub side, specifically in the homebrew-core repository.
Resolution: (issue once fixed but user reports resurfacing)
Maintainer of Homebrew reports that GitHub has identified and fixed the root cause of the issue. They have completed the repair operation on the homebrew-core repository, which should resolve the problem. Our monitoring has confirmed that the issue has been resolved so far but we see few user reporting the issue on following discussion on GitHub: brew update nonzero return value · Homebrew · Discussion #4612 · GitHub
Next Steps:
If you have been experiencing issues with brew update or encountering errors related to GitHub repositories, we recommend trying the command again.
The issue was once resolved but seems like few user are noticing resurfacing of the issue and reported here: brew update nonzero return value · Homebrew · Discussion #4612 · GitHub and seems like the Homebrew team and GitHub are working together to mitigate this issue.
We apologize for any inconvenience caused by this issue and appreciate your patience while it was being resolved. We will continue to monitor the situation closely and recommend user to report any issue.