Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/rubocop/rubocop/issues/11664 below:

Using a formatter or memory profile stops cache/parallelization from being used · Issue #11664 · rubocop/rubocop · GitHub

When you run

bundle exec rubocop --fail-level W --display-only-fail-level-offenses --cache true -d

the cache is used per the logs:

Use parallel by default.
Running parallel inspection
Loading cache from .rubocop-cache/rubocop_cache/REDACTED/REDACTED/REDACTED_FILE
Loading cache from .rubocop-cache/rubocop_cache/REDACTED/REDACTED/REDACTED_FILE

I expected running this

bundle exec rubocop --fail-level W --display-only-fail-level-offenses --cache true -d --format json
or
bundle exec rubocop --fail-level W --display-only-fail-level-offenses --cache true -d --format junit
or
bundle exec rubocop --fail-level W --display-only-fail-level-offenses --cache true -d --memory --profile

would do the same

It doesn't however, you get no lines regarding cache or parallel, only scanning

Scanning /Users/REDACTED/REDACTED/app/Gemfile
Scanning /Users/REDACTED/REDACTED/app/Rakefile
Scanning /Users/REDACTED/REDACTED/REDACTED_PATH/REDACTED_FILE.rb
Scanning /Users/REDACTED/REDACTED/REDACTED_PATH/REDACTED_FILE.rb

See commands above

1.47.0 (using Parser 3.2.1.0, rubocop-ast 1.27.0, running on ruby 2.7.7) [arm64-darwin21]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4