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
Various brew commands failing with Error: stack level too deep #2007
Comments
Try |
|
This is concerning. Make sure you've committed everything to all your branches and run |
I don't have any local changes that haven't merged upstream, so I ran |
What about the |
As I mentioned earlier, it works fine on the |
What's your |
With
|
This is still pretty weird and concerning. Have you always seen What does |
Closing due to no response. |
@MikeMcQuaid I've just experienced the same issue, most probably due to having contributed the formula I ran My question is: is that a required step after contributing a formula (i.e. something that contributors need to do), and if so, couldn't this be somewhat automated? Or is it just a bug? Here's my info before running
My config:
Please let me know if you need more info. |
It sounds like a bug. If you can create a reproducible set of commands after running |
I'm not sure how to recreate / reproduce it without actually contributing or updating a formula. But I'll keep this in mind next time opening a PR. |
|
Hi there,
Since I contributed updated formulae for Go (Homebrew/homebrew-core#9304 and Homebrew/homebrew-core#9305), various
brew
commands (including, sadly,brew doctor
) fail withError: stack level too deep
. I've runbrew update
twice, I've tried re-running the installation script. It seems that the problem occurs whenhomebrew-core
is not checked out on themaster
branch:This fixes it. I'm not sure why being on that branch (the state of which you can find here: https://github.com/tsuna/homebrew-core/tree/go-1.7.5) would cause this stack overflow error. How can I troubleshoot this further?
Not that I care much anyway, since I don't intend to stay on that branch as the changes have merged upstream anyway, but I found this error very confusing and not easy to root cause, and I'm puzzled as to why this would make various
brew
commands fail like that.The text was updated successfully, but these errors were encountered: