Problems running bundler installed standard and rubocop

[hurricup]

Gemfile:

source 'https://rubygems.org'
gem 'rubocop'
gem 'standard'

resolved to Gemfile.lock

GEM
  remote: https://rubygems.org/
  specs:
    ast (2.4.2)
    parallel (1.21.0)
    parser (3.0.2.0)
      ast (~> 2.4.1)
    rainbow (3.0.0)
    regexp_parser (2.1.1)
    rexml (3.2.5)
    rubocop (1.22.1)
      parallel (~> 1.10)
      parser (>= 3.0.0.0)
      rainbow (>= 2.2.2, < 4.0)
      regexp_parser (>= 1.8, < 3.0)
      rexml
      rubocop-ast (>= 1.12.0, < 2.0)
      ruby-progressbar (~> 1.7)
      unicode-display_width (>= 1.4.0, < 3.0)
    rubocop-ast (1.12.0)
      parser (>= 3.0.1.1)
    ruby-progressbar (1.11.0)
    standard (0.0.36)
      rubocop (>= 0.63)
    unicode-display_width (2.1.0)

PLATFORMS
  x86_64-linux

DEPENDENCIES
  rubocop
  standard

BUNDLED WITH
   2.2.26

When running:

bundle exec standardrb -a test.rb 
/home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml: Performance/RedundantSortBy has the wrong namespace - should be Style
/home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml: Performance/Sample has the wrong namespace - should be Style
/home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml: Rails/SafeNavigation has the wrong namespace - should be Style
bundler: failed to load command: standardrb (/home/user/.rvm/gems/ruby-3.0.2@rubocop/bin/standardrb)
/home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config_obsoletion.rb:43:in `reject_obsolete!': The `Layout/AlignArray` cop has been renamed to `Layout/ArrayAlignment`. (RuboCop::ValidationError)
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/AlignHash` cop has been renamed to `Layout/HashAlignment`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/AlignParameters` cop has been renamed to `Layout/ParameterAlignment`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/IndentArray` cop has been renamed to `Layout/FirstArrayElementIndentation`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/IndentAssignment` cop has been renamed to `Layout/AssignmentIndentation`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/IndentHash` cop has been renamed to `Layout/FirstHashElementIndentation`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/IndentHeredoc` cop has been renamed to `Layout/HeredocIndentation`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/LeadingBlankLines` cop has been renamed to `Layout/LeadingEmptyLines`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/Tab` cop has been renamed to `Layout/IndentationStyle`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Layout/TrailingBlankLines` cop has been renamed to `Layout/TrailingEmptyLines`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/DuplicatedKey` cop has been renamed to `Lint/DuplicateHashKey`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/EndInMethod` cop has been renamed to `Style/EndBlock`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/MultipleCompare` cop has been renamed to `Lint/MultipleComparison`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/StringConversionInInterpolation` cop has been renamed to `Lint/RedundantStringCoercion`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/UnneededRequireStatement` cop has been renamed to `Lint/RedundantRequireStatement`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/UnneededSplatExpansion` cop has been renamed to `Lint/RedundantSplatExpansion`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Naming/UncommunicativeBlockParamName` cop has been renamed to `Naming/BlockParameterName`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Style/UnneededCapitalW` cop has been renamed to `Style/RedundantCapitalW`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Style/UnneededCondition` cop has been renamed to `Style/RedundantCondition`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Style/UnneededInterpolation` cop has been renamed to `Style/RedundantInterpolation`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Style/UnneededPercentQ` cop has been renamed to `Style/RedundantPercentQ`.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Lint/UselessComparison` cop has been removed since it has been superseded by `Lint/BinaryOperatorWithIdenticalOperands`. Please use `Lint/BinaryOperatorWithIdenticalOperands` instead.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
The `Style/MethodMissingSuper` cop has been removed since it has been superseded by `Lint/MissingSuper`. Please use `Lint/MissingSuper` instead.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
`Performance` cops have been extracted to the `rubocop-performance` gem.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
`Rails` cops have been extracted to the `rubocop-rails` gem.
(obsolete configuration found in /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/config/base.yml, please update it)
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config_validator.rb:78:in `check_obsoletions'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config_validator.rb:44:in `validate'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config.rb:49:in `check'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config.rb:38:in `create'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config_loader.rb:55:in `load_file'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/rubocop-1.22.1/lib/rubocop/config_store.rb:29:in `options_config='
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/lib/standard/creates_config_store/assigns_rubocop_yaml.rb:6:in `call'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/lib/standard/creates_config_store.rb:17:in `block in call'
        from <internal:kernel>:90:in `tap'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/lib/standard/creates_config_store.rb:16:in `call'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/lib/standard/builds_config.rb:22:in `call'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/lib/standard/cli.rb:16:in `run'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/standard-0.0.36/exe/standardrb:7:in `<top (required)>'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/bin/standardrb:23:in `load'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/bin/standardrb:23:in `<top (required)>'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/cli/exec.rb:58:in `load'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/cli/exec.rb:58:in `kernel_load'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/cli/exec.rb:23:in `run'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/cli.rb:477:in `exec'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/cli.rb:31:in `dispatch'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/cli.rb:25:in `start'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/exe/bundle:49:in `block in <top (required)>'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/lib/bundler/friendly_errors.rb:128:in `with_friendly_errors'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/gems/bundler-2.2.26/exe/bundle:37:in `<top (required)>'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/bin/bundle:23:in `load'
        from /home/user/.rvm/gems/ruby-3.0.2@rubocop/bin/bundle:23:in `<main>'

[searls]

That's a very old version of Standard (one that had a more relaxed constraint on rubocop, which is why Bundler's solver apparently picked it. Please try running bundle update standard and if that doesn't work, set a version specifier of at least 1.0

[michaelglass]

something happened recently that installed exactly that ancient version of standard... Just commenting for posterity. I'm not exactly sure what I did 😅

If you add standard to your Gemfile after installing rubocop, you may end up with this ancient version which does not have an upper version bound for rubocop.

Subsequent versions of standard have max bounds on the rubocop version so if the Gemfile in your lockfile is too high, bundler will calculate that the ancient standard is a compatible version 😅

[markijbema]

Yeah I ran into this too. Took some googling to get here, but it gave me the first impression of an abandoned project. Maybe standard could release one special version in between serious releases (like rspec did with 2.99) which is compatible with all rubocop versions but just prints an instruction of what to do? Seems to me that switching from rubocop to standard is quite natural and it did not occur to me to remove the rubocop gems first

[searls]

That's a good idea @markijbema. It seems like our options are pretty limited.

We should probably consider a new release:

• With version 0.0.36.1 so it narrowly captures this edge case
• Specifies rubocop, > 0.63 (as opposed to >=, so it doesn't break things that legitimately are that old and intentionally lock rubocop@0.63 or earlier)
• That prints a long postinstall message to a link to a document explaining WTF is going on
• Prints a similar message every time it's run
• (Maybe?) prints a similar message every time it's loaded
• (Maybe?) raises an error every time it's run
• (Probably not?) raises an error every time it's loaded

Thoughts?

[michaelglass]

Are there cases when standard is loaded outside of the context of

• from its own executable
• within rubocop?

If so, then I guess it would make sense to avoid raising on load.

Otherwise, raising on load would reduce the noise of the subsequent slew of rubocop errors.

[searls]

Are there cases when standard is loaded outside of the context of

• from its own executable
• within rubocop?

No, but anyone who doesn't have require: false next to it in the Gemfile would see their process explode if they have Bundler require everything. The thinking of doing this would be that since people would only hit this if they first install or update the gem, if we can slam on the brakes for them right away before they've committed/pushed/moved on we can spare them confusion and frustration.

[searls]

Working on a version 0.0.36.1 now.

I've drafted this message and think it should run on postinstall as well as with every run of the CLI or rake tasks

WARNING: You do not want to run this very, very old version of Standard!

What's going on here?
---------------------
Versions of Standard prior to 0.0.37 depended on `>= 0.63' of RuboCop, which
means that Bundler continues to resolve to those (now ancient) versions when
whenever `gem "standard"' is added to a Gemfile that has already locked
to a newer version of RuboCop than standard currently depends on.

"How do I fix this?", you might be asking.

How to fix this
---------------
If you add a version specifier that pins `standard' to a version newer
than 0.0.36.1, Bundler will resolve the newest versions of `standard',
`rubocop', and any other rubocop-dependent gems you may have installed.

1. Update your Gemfile to pin standard to be at least one such version:

  gem "standard", ">= 1.0"

2. Run `bundle`, which will install and lock more appropriate versions

  Example output:
    Using rubocop 1.48.1 (was 1.49.0)
    Using rubocop-performance 1.16.0
    Using standard 1.26.0 (was 0.0.36)

We're very sorry for this inconvenience!

UPDATE: Simplifed the message

UPDATE 2: Simplified again

Feedback on this message?

[czeise]

Message is great. The problem is clearly explained as is the fix.

Small typo: There's an extra "when" in the "What's going on here?" section that should be removed:

...which means that Bundler continues to resolve to those (now ancient) versions when whenever `gem "standard"' is added to a Gemfile...

[searls]

Okay, I've released v0.0.36.1

If you add standard and Bundle resolves it for whatever reason, you'll see this:

$ bundle
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
Using ast 2.4.2
Using bundler 2.4.10
Using json 2.6.3
Using parallel 1.22.1
Using regexp_parser 2.7.0
Using rexml 3.2.5
Using unicode-display_width 2.4.2
Using ruby-progressbar 1.13.0
Using rainbow 3.1.1
Using parser 3.2.2.0
Using rubocop-ast 1.28.0
Using rubocop 1.49.0
Fetching standard 0.0.36.1
Installing standard 0.0.36.1
Bundle complete! 2 Gemfile dependencies, 13 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Post-install message from standard:
============================================================================
= WARNING: You do not want to run this very, very old version of Standard! =
============================================================================

What's going on here?
---------------------
Versions of Standard prior to 0.0.37 depended on `>= 0.63' of RuboCop, which
means that Bundler continues to resolve to those (now ancient) versions
whenever `gem "standard"' is added to a Gemfile that has already locked
to a newer version of RuboCop than standard currently depends on.

"How do I fix this?", you might be asking.

How to fix this
---------------
If you add a version specifier pinning `standard' to a version newer
than 0.0.36.1, Bundler will resolve appropriate versions of `standard',
`rubocop', and any other rubocop-dependent gems you may have installed.

1. Update your Gemfile to pin standard to be at least one such version:

  gem "standard", ">= 1.0"

2. Run `bundle`, which will install and lock more appropriate versions

  Example output:
    Using rubocop 1.48.1 (was 1.49.0)
    Using rubocop-performance 1.16.0
    Using standard 1.26.0 (was 0.0.36)

This version (0.0.36.1) is an inoperative placeholder gem that exists
solely to print this message.

We're very sorry for this inconvenience!

============================================================================
=                         END OF BIG SCARY WARNING                         =
============================================================================

You'll see the same message printed whenever the standardrb executable or standard rake tasks are invoked.

[sferik]

Might I be so bold to suggest yanking all gem versions of Standard prior to 0.0.37? On one hand, it’s possible that someone has a production deployment locked to one of these versions, which are now more than 4 years old. On the other hand, Standard shouldn’t be part of the production bundle and if you try running that version of Standard you get:

ArgumentError: Unknown Ruby version: 3.0

All versions of Ruby prior to 3.0 are EOL as of March 31, 2023, so anyone using this code is not only running a badly outdated version of Standard, they are also running a known insecure version of Ruby. If yanking Standard breaks someone’s deployment, that’s probably a good wakeup call to update Ruby before something much worse happens.

For your convenience, here is a command to generate a list of all the gem versions that should be yanked:

gem search '^standard$' --all | sed 's/[^0-9., ]*//g' | sed 's/,/\n/g' | xargs ruby -e 'ARGV.each { |version| puts version if Gem::Version.new(version) < Gem::Version.new("0.0.37") }'

According to Rubygems, people have run into this issue nearly 5,000 times over the past 4 months.

[searls]

@sferik thanks for this comment, Erik.

This is really tough for me, because I am a pretty firm believer that package repositories should be write-only and relied upon as immutable as a matter of principle. But the practical reality of how Bundler's solver currently works is that the existence of these old releases is causing a significant amount of harm to people for (if I'm being honest) an at-best theoretical benefit of keeping every release up in perpetuity on RubyGems.

After thinking about it overnight, I'm 👍 on doing this.