Closed stevenchanin closed 6 years ago
Exactly this stacktrace has an unresolved, upstream issue https://github.com/SublimeLinter/SublimeLinter/issues/1061
Its also not clear to me why running a test(s) would trigger sublimelinter / rubocop at all?
Maybe these commands trigger a save or a modified event.
Can you set "kill_old_processes": true,
in your SublimeLinter user settings.
Thanks very much for the quick response and the suggestion.
Ok. I just added "kill_old_processes": true
to the SublimeLinter user settings. I'll let you know what I see today.
Not sure this is a rubocop problem, but I'm seeing intermittent crashes when I run rspec tests from within sublime after upgrading to 3170.
For example, I just tried to run a single test (cmd-R) in a file called
placer_spec.rb
and I got the following in the sublime console:However, the next time I ran that test, I didn't get any complaints from rubocop/sublime linter. Sometimes I get that crash message running a rspec on a full file (cmd-T). And sometimes it works. I haven't seen a pattern.
Its also not clear to me why running a test(s) would trigger sublimelinter / rubocop at all?
Versions
Rubocop -- 0.55.0 RubyTest Package -- v2107.08.22.09.18.19 SublimeLinter -- v4.5.0 SublimeLinter-rubocop - v2.0.4