-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ArgumentError: wrong number of arguments (given 1, expected 0) #6326
Comments
Thank you, it seems like a "typo" in PubGrub, where the I'll provide a fix. |
Saw this after creating an issue on pub_grup. |
I was playing around with this and found a smaller repro, in case it's helpful for writing a failing test: source "https://rubygems.org"
gem "google-protobuf"
gem "unf_ext"
Running The |
Thanks to the helpful repro by @composerinteralia I managed to write a spec for this! |
Describe the problem as clearly as you can
Running
bundle update
results in the following error:Did you try upgrading rubygems & bundler?
This gives the same "ArgumentError" as the
bundle update
command on its own.Post steps to reproduce the problem
Run the
bundle update
command.Which command did you run?
bundle update
What were you expecting to happen?
The Gemfile to be updated.
What actually happened?
Environment
Bundler Build Metadata
Bundler settings
Gemfile
Gemfile
Gemfile.lock
If not included with the output of your command, run
bundle env
and paste the output belowIncluded above.
The text was updated successfully, but these errors were encountered: