Expected Behavior

When Rubocop encounters '"' + "foo" + '"' it should be autocorrected to '"foo"'

Actual Behavior

When Rubocop 1.1.0 encounters '"' + "foo" + '"' it currently autocorrects to ""foo"" thus leading to a syntax error:

test.rb:3:3: C: [Corrected] Style/StringConcatenation: Prefer string interpolation to string concatenation.
p '"' + "foo" + '"'
  ^^^^^^^

Affects PMD Version: 6.30.0-SNAPSHOT

Rule: JUnitAssertionsShouldIncludeMessage

Description:

From pmd/pmd#2871 (comment)

Code Sample demonstrating the issue:

https://chunk.io/pmd/fc7db65b2c6a46eca4c9a0c3012482e2/diff/spring-framewo

Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate pytype into ALE and this would make it a lot easier.

That is: org.springframework.beans.factory.annotation.Autowired

Writing this mostly as a reminder to self. But if anyone else wants to do it, it should be a trivial change.

Describe the bug
In the docs found here:
https://bandit.readthedocs.io/en/latest/plugins/index.html#complete-test-plugin-listing

B109 and B111 show a description instead of a plugin name. This looks inconsistent since all the other plugin names are listed. I believe this is a result of a recent change to remove these deprecated plugins.

To Reproduce

1. Navigate to https://bandit

The Problem

With the new model-property type and ModelPropertyRule Larastan now has the ability to check the existence of model columns that are given to a method.

Adding the model-property type to the Laravel's core methods are done with the help of PHPstan stubs. Some [examples](https://github.com/nunomaduro/larastan/blob/master/stubs/Elo

It looks like eval is a special case in our PHP parsing:

$ echo 'eval("echo foo");' | python -m semgrep --lang php --pattern 'evaz(...);' -
ran 1 rules on 1 files: 0 findings

$ echo 'eval("echo foo");' | python -m semgrep --lang php --pattern 'eval(...);' -
semgrep error: invalid pattern
  --> CLI Input:1
1 | eval(...);
  | ^^^^^^^^^

Pattern could not be parsed as a 

fainal should be final.

https://spotbugs.readthedocs.io/ja/latest/bugDescriptions.html?highlight=fainal#ci-final-protected-ci-confused-inheritance

このクラスは， final と宣言されていますが，フィールドは protected と宣言されています。 クラスは fainal なので派生できません。protected の使用は紛らわしいです。 フィールドのためのアクセス修飾子は，フィールドの真の用途を表すため， private か public に変更すべきです。

I can't fix this, because I don't have permissions for adding fix on Read the D

I wrote some of the code to do this in a branch https://github.com/python-security/pyt/compare/class_based_views, but since I'm working on other things and this feature seems cool and important I'm making this issue 👍

Let me know if you would like any help in implementing.

Rubberduck version information

Version 2.5.0.5524
OS: Microsoft Windows NT 10.0.18362.0, x64
Host Product: Microsoft Office 2016 x64
Host Version: 16.0.5026.1000
Host Executable: EXCEL.EXE

Description
When pressing the tab key after preforming a search in Add/Remove references a "Null Reference" error occurs. Pressing tab in other locations will also cause this error. Also, when

As shown in #204, there's a need to being able to disable the UID and GID checks of the "Container Security Context" check without disabling the other checks that are made. I'm therefore proposing to split this check into three separate ones:

• Container Security Context User/Group