Closed pboling closed 11 months ago
Note: The same issue occurs when running the executable instead of the rake task, so that's not relevant.
I replaced the byebug with a puts
:
rescue NoMethodError => error
puts "skipping nil str"
# byebug
end
And then I got this:
Inspecting 32 file(s) for autocorrection...
................................
Fixed 0 file(s).
................................
Found 3 files with 40 issue(s).
Processing results...
skipping nil str
RuboCop Gradual got results for the first time. 40 issue(s) found.
Don't forget to commit `.rubocop_gradual.lock` log file.
So it clearly only failed the one time.
Here is the repo with the repro (link to GH Actions that failed - the error isn't very helpful, hence my local byebug)
Hey, @pboling thanks for kind words!
Actually the fix was already in master π I just released a new version of the gem (0.3.2), so you can update your version and update/regenerate your lock file since this line lacks the hash value
Wonderful!
Firstly, I need to say: I love this gem - the idea is brilliant, and I'd love to help however I can!
I hacked the gem source to see what was going on:
Before hitting my
byebug
, I got this output:I am not familiar with that last line, having run rubocop_gradual many times now.
Here's some introspection after hitting my
byebug
:I am not sure which file it is dying on... because
str
isnil
... π