-
Notifications
You must be signed in to change notification settings - Fork 54
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
wrong number of arguments #206
Comments
Hi @sobrinho. Can you give me an example of the test you're trying to write? That would help me understand what caused this. |
There's nothing too specific there, it's a simple A lot of different specs with different assertions are failing. Not sure if it's related to Ruby 2.7.6, I'm trying to isolate it. |
Hey @sobrinho , thanks for the report! First, a note that since Ruby 2.7 has reached end of life, we don't support it any more. But this may be applicable to the latest version anyway. I did rewind to Ruby 2.7.6, SuperDiff 0.9.0, and fast-forwarded to attr_extras v7.1.0, and was still unable to reproduce this with RSpec 3.9.0 or 3.10.0. Here's my repro file: require 'super_diff/rspec'
RSpec.describe do
it do
something = Struct.new(:blah).new
expect(something).to receive(:blah).with(1)
something.blah(2)
end
end and here's the output I got:
Let me know if you're able to reproduce this again. I wonder if the object you're stubbing has some interesting behavior that would make it difficult to inspect, so a full backtrace with the other gems would be good too. |
Another note: possibly related to #140 – stack trace looks very similar. |
Hi there!
I'm seeing this error:
The backtrace after that goes in other gems, let me know if you need it.
The text was updated successfully, but these errors were encountered: