[ https://issues.apache.org/jira/browse/HBASE-27026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541129#comment-17541129 ]
Jan Hentschel commented on HBASE-27026: --------------------------------------- Not sure. I would have expected that your [second commit|https://github.com/apache/hbase/pull/4416/commits/71b2f9670b205252b6bb7357265995c2d554e864] would be ok from a Rubocop perspective. It definitely could be related to the version as it seems that Rubocop also makes adjustments to the rules. > Disable Style/FrozenStringLiteralComment for ruby > ------------------------------------------------- > > Key: HBASE-27026 > URL: https://issues.apache.org/jira/browse/HBASE-27026 > Project: HBase > Issue Type: Task > Reporter: Tao Li > Assignee: Tao Li > Priority: Major > Attachments: image-2022-05-20-09-14-36-355.png, > image-2022-05-20-09-25-05-608.png > > > By default Style/FrozenStringLiteralComment is enabled in rubocop. If we > update a ruby file, rubocop prompts `Missing frozen string literal comment` > (see > [https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4416/2/artifact/yetus-general-check/output/diff-patch-rubocop.txt)|https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4416/2/artifact/yetus-general-check/output/diff-patch-rubocop.txt]. > To address this warn, we need to add `# frozen_string_literal: true` to the > top of the ruby file(see > https://github.com/rubocop/rubocop/blob/master/config/default.yml#L3637), > which will be added to the top of the `Apache License` and will look strange. > I don't think this `FrozenStringLiteralComment` check is very necessary. We > can disable it. -- This message was sent by Atlassian Jira (v8.20.7#820007)