Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StandardRB 1.44.0 breaks Ruby LSP integration with unrecognized cop errors #691

Open
jacobduba opened this issue Jan 26, 2025 · 2 comments

Comments

@jacobduba
Copy link

Description

After upgrading from Standard Ruby 1.43.0 to 1.44.0, the Ruby LSP integration breaks with numerous "unrecognized cop" errors. The issue persists even after downgrading back to 1.43.0 unless the gem is completely removed and reinstalled.

Environment

  • Ruby version: 3.3.6
  • Standard Ruby version: 1.44.0
  • Ruby LSP version: 0.23.6
  • RuboCop version: 1.70.0

Steps to Reproduce

  1. Start with a working setup using Standard Ruby 1.43.0
  2. Upgrade to Standard Ruby 1.44.0
  3. Attempt to use Ruby LSP

Current Behavior

The Ruby LSP fails to initialize with hundreds of "unrecognized cop" errors, starting with:

Error loading addons:
/var/home/jduba/Bench/vipreply.ai/vendor/bundle/ruby/3.3.0/gems/rubocop-1.70.0/lib/rubocop/cop/registry.rb:68:in `dismiss': Cop RuboCop::Cop::Cop could not be dismissed (RuntimeError)

Followed by numerous errors like:

unrecognized cop or department Bundler/DuplicatedGem found in /var/home/jduba/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/standard-1.44.0/config/base.yml

Workaround

I found this workaround:

  1. Remove Standard Ruby completely
  2. Reinstall version 1.43.0

Simply downgrading the version without removal doesn't resolve the issue.

@camilopayan
Copy link
Contributor

How strange we ran into that problem while upgrading, and fixed the issue, which is around the namespace iirc. I'll look into it, thanks.

@jacobduba
Copy link
Author

Thanks! LMK if there's any more information / tests I can do to help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants