You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the internal logic tries to change existing string when # frozen_string_literal: true is present and output_style is set to block. Did not try to dig deeper, but here is the stacktrace:
Traceback (most recent call last):
5: from .../.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/simplecov-0.18.5/lib/simplecov/defaults.rb:27:in `block in <top (required)>'
4: from .../.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/simplecov-0.18.5/lib/simplecov.rb:202:in `at_exit_behavior'
3: from .../.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/simplecov-0.18.5/lib/simplecov.rb:214:in `run_exit_tasks!'
2: from .../.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/simplecov-0.18.5/lib/simplecov/configuration.rb:196:in `block in at_exit'
1: from .../.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/simplecov-0.18.5/lib/simplecov/result.rb:49:in `format!'
.../.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/simplecov-console-0.7.0/lib/simplecov-console.rb:79:in `format': can't modify frozen String (FrozenError)
The text was updated successfully, but these errors were encountered:
Pretty much in every ruby file both in my personal as well as work related projects I use the frozen string literal comment on top of the ruby files which is enforced by rubocop rule.
I would imagine many projects do that as it might become the default behavior in future ruby versions.
Looks like the internal logic tries to change existing string when
# frozen_string_literal: true
is present andoutput_style
is set toblock
. Did not try to dig deeper, but here is the stacktrace:The text was updated successfully, but these errors were encountered: