Skip to content
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

Closed
4 tasks done
Dids opened this issue Sep 30, 2020 · 16 comments
Closed
4 tasks done

brew update failing (transfer closed with outstanding read data remaining) #61772

Dids opened this issue Sep 30, 2020 · 16 comments

Comments

@Dids
Copy link

Dids commented Sep 30, 2020

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:

git config --global http.postBuffer 524288000

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?

  • ran brew update and can still reproduce the problem?
  • ran brew doctor, fixed all issues and can still reproduce the problem?
  • ran brew gist-logs <formula> (where <formula> is the name of the formula that failed) and included the output link?
  • if brew gist-logs didn't work: ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)

Run brew update.

What happened (include command output)

> brew update
fatal: unable to access 'https://github.com/Homebrew/homebrew-core/': transfer closed with outstanding read data remaining
Error: Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core failed!

What you expected to happen

Homebrew update should have succeeded.

Step-by-step reproduction instructions (by running brew install commands)

brew update

Output from brew config and brew doctor

HOMEBREW_VERSION: 2.5.1
ORIGIN: https://github.com/Homebrew/brew
HEAD: c7e4a3d8b9835a94edb3a6744b6f66cac06cf064
Last commit: 2 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 97dbb4fc16488ad5ba63ee24d52ab3f8c92442c5
Core tap last commit: 12 days ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: ["--no-quarantine"]
HOMEBREW_COLOR: set
HOMEBREW_MAKE_JOBS: 4
HOMEBREW_NO_AUTO_UPDATE: set
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: quad-core 64-bit ivybridge
Clang: 11.0 build 1103
Git: 2.28.0 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 14.0.2, 13.0.2, 12.0.2, 11.0.8, 1.8.0_265, 1.7.0_272
macOS: 10.15.6-x86_64
CLT: 12.0.0.0.1.1599194153
Xcode: 11.7 => /Applications/Xcode_11.7.app/Contents/Developer
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
  /usr/local/lib/libtcl8.6.dylib
  /usr/local/lib/libtk8.6.dylib

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/fakemysql.h
  /usr/local/include/fakepq.h
  /usr/local/include/fakesql.h
  /usr/local/include/itcl.h
  /usr/local/include/itcl2TclOO.h
  /usr/local/include/itclDecls.h
  /usr/local/include/itclInt.h
  /usr/local/include/itclIntDecls.h
  /usr/local/include/itclMigrate2TclCore.h
  /usr/local/include/itclTclIntStubsFcn.h
  /usr/local/include/mysqlStubs.h
  /usr/local/include/odbcStubs.h
  /usr/local/include/pqStubs.h
  /usr/local/include/tcl.h
  /usr/local/include/tclDecls.h
  /usr/local/include/tclOO.h
  /usr/local/include/tclOODecls.h
  /usr/local/include/tclPlatDecls.h
  /usr/local/include/tclThread.h
  /usr/local/include/tclTomMath.h
  /usr/local/include/tclTomMathDecls.h
  /usr/local/include/tdbc.h
  /usr/local/include/tdbcDecls.h
  /usr/local/include/tdbcInt.h
  /usr/local/include/tk.h
  /usr/local/include/tkDecls.h
  /usr/local/include/tkPlatDecls.h

Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
  /usr/local/lib/pkgconfig/tcl.pc
  /usr/local/lib/pkgconfig/tk.pc

Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
  /usr/local/lib/libtclstub8.6.a
  /usr/local/lib/libtkstub8.6.a
@sebastianw
Copy link
Contributor

Yeah noticed the same problem this morning.

@miccal
Copy link
Member

miccal commented Sep 30, 2020

Thank you @Dids and @sebastianw for the reports.

The maintainers of brew are aware of this issue and have lodged support tickets with GitHub, so it is being investigated.

@Francegala
Copy link

Screenshot 2020-09-30 at 16 12 17

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
fatal: unable to access 'https://github.com/Homebrew/homebrew-cask/': transfer closed with outstanding read data remaining
Error: Failure while executing; git clone https://github.com/Homebrew/homebrew-cask /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask exited with 128.
(In case I need to raise another issue, just let me know)

@seanwang-okta

This comment has been minimized.

@madebyamin

This comment has been minimized.

@iMichka
Copy link
Member

iMichka commented Sep 30, 2020

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.

@minwook-shin
Copy link

Same issue for me, but it works now.
try brew update && brew upgrade.

@Rylan12
Copy link
Member

Rylan12 commented Oct 2, 2020

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.

@SMillerDev
Copy link
Member

Closing this since it seems to be resolved.

@alebcay alebcay unpinned this issue Oct 3, 2020
@Djadih
Copy link

Djadih commented Oct 9, 2020

Unfortunately still happening for me. Here's my output:

fatal: unable to access 'https://github.com/Homebrew/homebrew-core/': transfer closed with outstanding read data remaining
Error: Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core failed!

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.

@timolehto
Copy link

I can confirm too, it's still happening.

@Dids
Copy link
Author

Dids commented Oct 9, 2020

Indeed, this was fine for about a week, but largely just failing today.

@iMichka
Copy link
Member

iMichka commented Oct 9, 2020

As said above:

It's a GitHub issue. Not a homebrew issue.

@tigertim08
Copy link

I'm having the same Issue here, so not solved yet

@Homebrew Homebrew locked as off-topic and limited conversation to collaborators Oct 9, 2020
@iMichka
Copy link
Member

iMichka commented Oct 9, 2020

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.

@alebcay
Copy link
Member

alebcay commented Oct 9, 2020

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.

@alebcay alebcay pinned this issue Oct 9, 2020
@dtrodrigues dtrodrigues unpinned this issue Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests