standardrb/standard · error · Standard::Lsp::StdinRubocopRunner::ConfigurationError

error.message

Error message

error.message

What it means

Error "error.message" thrown in standardrb/standard.

Source

Thrown at lib/standard/lsp/stdin_rubocop_runner.rb:51

      end

      def run(path, contents)
        @errors = []
        @warnings = []
        @offenses = []
        @options[:stdin] = contents

        super([path])

        raise Interrupt if aborting?
      rescue ::RuboCop::Runner::InfiniteCorrectionLoop => error
        if defined?(::RubyLsp::Requests::Formatting::Error)
          raise ::RubyLsp::Requests::Formatting::Error, error.message
        else
          raise error
        end
      rescue ::RuboCop::ValidationError => error
        raise ConfigurationError, error.message
      rescue => error
        if defined?(::RubyLsp::Requests::Formatting::Error)
          raise ::RubyLsp::Requests::Support::InternalRuboCopError, error
        else
          raise error
        end
      end

      def formatted_source
        @options[:stdin]
      end

      private

      def file_finished(_file, offenses)
        @offenses = offenses
      end
    end

View on GitHub (pinned to c93189e2b3)

Solutions

1. Fix the invalid RuboCop configuration that raised the RuboCop::ValidationError: check .rubocop.yml and .standard.yml for unknown cops, bad values, or misspelled keys, then re-run StandardRB.
2. Run rubocop or standardrb directly to surface the underlying validation error with its full context.
3. If a plugin defines custom cops, ensure the plugin gem is loaded and its config validates against the installed RuboCop version.

When it happens

Trigger: Thrown at lib/standard/lsp/stdin_rubocop_runner.rb:51 when the library encounters an invalid state.

Common situations: Defense: standardrb's LSP formatting path rescues RuboCop::ValidationError and re-raises it as ConfigurationError. Occurs when RuboCop validates the merged config and finds an unknown cop name, an invalid parameter value, or an obsolete configuration key. Check your .standard.yml and any plugin-supplied config for cop names or settings that the installed rubocop/rubocop-ast versions no longer recognize; run `standardrb` directly (not via the editor LSP) to see the full validation error and offending key.

AI-assisted analysis of standardrb/standard@c93189e2b3 (2026-08-23). Data as JSON: /api/errors/c5d9a535692ecadd. Report an issue: GitHub.