Jon Rowe

Make sure you are not passing hashes as kwargs, this is not valid on Ruby 3 and is now detected correctly (but the diff doesn't show the delta correctly on...

Our support for keyword arguments isn't as good as it could be, a lot of usage such as yours has historically just worked due to implementation details of Ruby (mainly...

Oddly I can't replicate this within our test suite on either `2.7.4`, `2.7.5` or `3.1.0` Edit: Removed output showing the snippet didn't work, it needed this adding for reproduction: ```...

@benoittgt This PR is just demonstrating the issue, it still needs fixing.

I'd prefer either adding a block that flips the config e.g you default to strict but run certain examples with: ``` around(:example) { |ex| use_truthy_predicate_matchers { ex.call } } ```...

> I assume that's necessary for the broad error-handling rspec has to do to properly catch and expose the exceptions produced by the code under test as being separate from...

What ordering are you using? The bisect relies on consistent ordering and the check is quite basic, it just checks that the bisects sub ordering is the same as it...

What OS / filesystem are you using? What filters if any are you applying? You haven't provided any steps to reproduce this so its a bit hard to determine what...

Are you comfortable monkey patching? The easiest way would be to apply this patch to see why the output is changing: ``` module DebugMonkeyPatch def abort_if_ordering_inconsistent(results) expected_order = all_example_ids &...

If you put that in a file in your directory and require it in your spec_helper it should run with the bisector and output the ordering.