Thijs de Vries

We could always do what https://github.com/CanCanCommunity/cancancan and make a new library (the original library was cancan which met a similar end).

I think it works if you do `Gsearch searchTerm ./` If you do `Gsearch searchTerm` it uses `*` for files which ignores the ignores.

Reading up on https://docs.cypress.io/guides/guides/parallelization, I think this may be a side effect on how cypress load balances things. Things aren't evenly split up in a deterministic way, it tries to...

I can't comment since I don't work for cypress but this part https://docs.cypress.io/guides/guides/parallelization#CI-parallelization-interactions makes me think that each individual container won't always run the same tests. The re-run is just...

@tebeco is it that it doesn't parallelize or that only one of the containers failed so all the tests get run in that one container? I'd have to try a...

Trying to use the `InputObject` solution doesn't appear to work for me. It tries to find the policy for the mutation and not the instance that is returned in the...

@nthx the following seemed to have work for me (I put this in a config/initializers file in my rails app): ``` ruby require 'redis/namespace' Redis::Namespace::COMMANDS['lock'] = :all Redis::Namespace::COMMANDS['unlock'] = :all...

I'd even love if this could be enabled for "safe" auto correctable. I've been bitten by rubocop bugs where something wasn't as safe as it claimed to be. I've seen...

Okay, so for "reducing its scope to those forbidden calls directly under example groups (and inside iterators directly under example groups)", right now I detect whether something is in an...

Another alternative would be to make assumptions about receiver. Other than the initial `RSpec.describe`, rspec blocks usually have a nil receiver. We could forbid calls inside describe blocks in same...