-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
brew update failing (transfer closed with outstanding read data remaining) #61772
Comments
Yeah noticed the same problem this morning. |
Thank you @Dids and @sebastianw for the reports. The maintainers of |
When installing homebrew I had the same issue then I realised it's not just the brew update, but any installation "brew cask install" returns the error |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
It's a GitHub issue. The homebrew maintainers are also impacted by this right now. We have reported the issue to Github and are waiting for feedback. |
Same issue for me, but it works now. |
I believe the issue has been fixed. Several maintainers (including myself) have been able to push/pull successfully today and our CI system seems to be working again. I haven't received an official response from GitHub indicating the issue's been fixed, though, so it's possible that they are still working on it in some capacity. If you were having trouble previously, I would recommend giving it another try now. |
Closing this since it seems to be resolved. |
Unfortunately still happening for me. Here's my output:
Brew doctor says system is ready to brew. Pretty strange. I admit I haven't used brew in a few weeks until now, not sure if that matters. |
I can confirm too, it's still happening. |
Indeed, this was fine for about a week, but largely just failing today. |
As said above:
|
I'm having the same Issue here, so not solved yet |
I am locking this issue. The timeouts are a Github issue, so you all need to report it to Github. Adding a "it's broken for me too" comment does not help moving things forward, and just pollutes the maintainer's notifications with useless messages. Sorry but we as homebrew maintainers can't do anything about this bug. |
Just to provide an update, we've reached out to GitHub again and their engineering team is looking at this once again. However, like previously mentioned, there's nothing we can do on our end to fix this issue, so please sit tight. We maintainers are crossing our fingers as hard as everyone else is at this time. |
Bug report
Ever since this morning, I noticed
brew update
failing repeatedly on my local machine.Next I tried it on a second machine, where it was also failing.
Eventually I also saw this while running GitHub Actions CI jobs, where it was failing exactly like on my local machine, which sounds like it's a global problem, not a local problem.
Ultimately this was fixed by the following git configuration change:
UPDATE: Even after the above change, I'm still seeing occasional failures, unless this is entirely on GitHub's side and nothing to do with brew per se?
brew update
and can still reproduce the problem?brew doctor
, fixed all issues and can still reproduce the problem?brew gist-logs <formula>
(where<formula>
is the name of the formula that failed) and included the output link?brew gist-logs
didn't work: ranbrew config
andbrew doctor
and included their output with your issue?What you were trying to do (and why)
Run
brew update
.What happened (include command output)
What you expected to happen
Homebrew update should have succeeded.
Step-by-step reproduction instructions (by running
brew install
commands)Output from
brew config
andbrew doctor
The text was updated successfully, but these errors were encountered: