Crash with some formatters in v1.63.2 about rubocop HOT 5 CLOSED

I noticed when looking at the --debug output that the file with the Lint/EmptyFile error was being loaded from the rubocop cache. So I turned off the cache and rubocop ran successfully to completion.

So it would seem that perhaps this is problem with the data I have in my cache.

Is that sufficient resolution to this? Shall I just close the issue?

The contents of that cached file is:
[{"severity":"warning","location":{"begin_pos":0,"end_pos":0},"message":"Lint/EmptyFile: Empty file detected.","cop_name":"Lint/EmptyFile","status":"unsupported"}]

from rubocop.

I can reproduce this by creating a new empty file and running rubocop on it twice. Only the second run will error. Lint/EmptyFile creates a global offense which I presume doesn't roundtrip well. This is now exposed because of #12804.

from rubocop.

@Earlopain interestingly (to me at least) This problem only happens when caching is involved.

I moved aside my cache directory and ran rubocop with the debug flag. It ran fine and I could see my empty file was being scanned. I ran a few more times immediately and the next 2 or 3 times the file was still scanned but then the file was being picked up by the cache and rubocop was crashing.

from rubocop.

Check out the attached PR, that should fix this. Let me know if that works for you.

from rubocop.

Check out the attached PR, that should fix this. Let me know if that works for you.

This does appear to correct the problem.

from rubocop.