-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
curl error when attempting to fetch issues from github for custom tap #2733
Comments
This would be where the change should be made: brew/Library/Homebrew/utils/github.rb Lines 270 to 273 in b9cfd2c
Closing as we don't support GitHub Enterprise but we'll accept a fix for this case. |
Don't need to support issues for GHE. (I can see that being a huge pain in not knowing which version of the API any particular GHE instance was using.) But brew already supports taps for any given remote (as evidenced by the |
I don't think this method necessarily implies "not on GitHub".
Yes. If this problem is reported more widely I'll look at fixing it but otherwise I'll leave it to those affected to work on the fairly straightforward fix. |
Fair. (A github-hosted tap that doesn't follow the homebrew-{repo} convention would be considered a However, this documentation clearly indicates that non-github taps are supported.
But again, I think it's totally fair to define "support" of a non-github tap as: "will not perform the niceties like fetching open issues on formula failure". But I strongly think that brew shouldn't be throwing exceptions when it encounters non-github taps. Especially when documentation indicates they are a supported (though second-class) use case. I'll work on a PR to fix! |
Without being too much of a dick about it: that's a bad assumption. Things maintainers say are supported are supported.
That's great, thanks. |
I'm not trying to be contentious here, but the claim that non-github taps aren't supported is in direct contradiction to all the documentation in the repo and in brew's own manpages. Obviously, if you say they're unsupported, then they're unsupported. But all the documentation below indicates (unequivocally) that they are supported. Was support dropped recently and the docs need updated to reflect the change? docs/How-to-Create-and-Maintain-a-Tap.md
brew-tap manpage (literally says "can be cloned from places other than GitHub")
|
I think we're just disagreeing over what the word "supported" means. To me, it means "things that we will prioritise fixing if it's broken" (and "we" mostly means "@MikeMcQuaid" on Homebrew/brew). To others it means, "all documented Homebrew functionality". I don't agree with this; we document things that people want and try to do even but they are not the "happy path" that we recommend. For example, installing Homebrew into a non-/usr/local location is functional but not supported; we may fix issues you have with it or we may not. |
Okay, I can understand that. And the spectrum of "support" makes sense. Even with this bug, I would never expect non-github taps to fetch open issues, as github.com taps do. Thanks! |
Thought I'd add that |
Please always follow these steps:
Confirmed this is a problem with running a
brew
command and justbrew install
ing one or more formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/newRan
brew update
and retried your prior step?Ran
brew doctor
, fixed all issues and retried your prior step?Ran
brew config
andbrew doctor
and included their output with your issue?brew-config output
Please note we may immediately close your issue without comment if you delete or do not fill out the issue checklist and provide ALL the requested information.
To help us debug your issue please explain:
What you were trying to do (and why)
Attempting to install a formula from a custom tap. Important detail: the custom tap is hosted on our internal GitHub Enterprise instance.
What happened (include command output)
Received 2 bits of error output. The first was some error output from the failed formula itself (which was expected). The second was error output from a failed
curl
command while brew was attempting to fetch related issues from the tap. Full command outputrelevant snippet:
What you expected to happen
Expected just the error output from the formula. (ie, the error output from
make
) Brew should not be attempting to fetch issues from api.github.com for taps which are not on public github.Step-by-step reproduction instructions (by running
brew
commands)I would imagine this is where the additional guard should take place:
brew/Library/Homebrew/exceptions.rb
Line 418 in b9cfd2c
It should be checking if the tap has a
custom_remote?
and/or if the tap is aprivate_repo?
(which is currently not exposed on aTap
but probably should be?)The text was updated successfully, but these errors were encountered: