Style/MethodDefParentheses only finds offense 1 per core

[emailrhoads]

There is a strange issue that is occurring where when we run rubocop it only finds a few offenses each time. This is particularly annoying because it requires an iterative approach to resolve all issue.

Style/MethodDefParentheses appears to be the particular cop causing this problem.

---

Expected behavior

I expect the results for bundle exec rubocop to find all violation of all cops across all files

Actual behavior

When I run bundle exec rubocop, I get 1 offense
When I run bundle exec rubocop -P, I get 4 offenses (one for each core)

Steps to reproduce the problem

We are not using a Gemfile.lock in this instance (want latest versions of everything).

RuboCop version

Include the output of rubocop -V or bundle exec rubocop -V if using Bundler. Here's an example:

$ sudo bundle exec rubocop -V
0.89.1 (using Parser 2.7.1.4, rubocop-ast 0.3.0, running on ruby 2.5.7 x86_64-linux)

[rpbaltazar]

I'm also facing this. Also, I need to run with cache disabled otherwise it won't even detect anything else.

It's a bit silly, but i ended up by writing a bash script to run rubocop in a loop auto correcting the offenses:

# /bin/bash
x=0
while [ $x -eq 0 ]
do
  rubocop -C false -a | grep 'offense detected' &> /dev/null
  x=$?
  echo "Finished $x"
done
echo $x

https://gist.github.com/rpbaltazar/80f95c6deda17dbd06905c213cede041

[jsmestad]

Wanted to say I am hitting this as well. Tried 0.90.1, 0.90.0 and 0.89.0 if that is helpful to see where the issue is.

To expand though I am seeing this with Layout/DotPosition and Layout/SpaceAroundEqualsInParameterDefault

[rdunlop]

@jsmestad I think that I may have a handle on this one too. see #8817