static-code-analysis

For the rule documentation page, there are currently two descriptions being shown: one right under the page title and one under the table of contents. Two tasks for each rule:

1. The one under the table of contents is hardcoded into the markdown files and should be removed. These files are all in docs/src/rules.
2. The one under the title is pulled from the rule's meta information, so we nee

There are some annoying warnings when building the documentation site:

$ antora --pull antora-playbook.yml
asciidoctor: WARNING: skipping reference to missing attribute: 1
asciidoctor: WARNING: skipping reference to missing attribute: 3
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: W

Is your feature request related to a problem? Please describe.
When a test fails and there are numerous expected lines to be detected, the output is really not helpful and it's hard to quickly see which lines were missed and/or incorrectly detected:

	✖ test-rule    expected lines: [4, 7, 10, 13, 17, 20, 23, 26, 29, 32, 35, 38, 41, 44, 47, 51, 57, 59, 63, 67, 70, 73, 76, 78, 80, 83, 85

Describe the solution you'd like

Validate test commands arguments before Run. This pattern will allow us to governance behaviors such as flags/arguments validation in all commands. Additionally, this should make the code easier to understand and maintain.

Requirements
Golang basic level.

“How to Implement” suggestion

See [issue](datreeio/datree#4

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. create .bandit file with content:

[bandit]
tests: B101,B102,B301

2. run bandit -c .bandit -r module/
3. get error:
   [main] ERROR .bandit : Error parsing file.

Expected behavior
working as described in readme

Bandit version

ba

Current problem

The representative code implements single dispatching with the @singledispatch and @staticmethod decorators in a class.

Class Board():

   @singledispatch
   @staticmethod
   def convert_position(position):
        [...]
   
    @convert_position.register(str)
    @staticmethod
    def _(position: str) -> tuple:
        [...]

    @convert_p

Affects PMD Version: 6.44

Rule: ImmutableField

Description: Per Java EE spec (https://docs.oracle.com/javaee/6/tutorial/doc/bnbqa.html) Java entity classes must not be declared final. Likewise no methods or persistent instance variables must be declared final. The last part is especially true for this rule

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.

Is your feature request related to a problem? Please describe.

Our code-base has error strings that are not being checked by error-strings.

Describe the solution you'd like

Currently, error-strings uses a hardcoded list of functions that it checks. We use an interna

This would allow for more localized suppressions. Say we have a method foo(Object o) in an annotated third-party library where o has no type annotation, but o really should be @Nullable, as foo() can handle being passed null as a parameter. In code checked by NullAway, say you write:

void bigMethod() {
  ...
  foo(null); // NullAway reports an error
  ...
}

I beli

[spotbugs] Running SpotBugs...     
    [spotbugs] Unexpected problem occured during version sanity check         
    [spotbugs] Reported exception:         
[spotbugs] java.lang.AbstractMethodError: Receiver class org.slf4j.nop.NOPServiceProvider does not define or inherit an implementation of the resolved method 'abstract java.lang.String getRequesteApiVersion()' of interface org.slf4j.

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
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Rubberduck version [Version 2.5.2.6030
OS: Microsoft Windows NT 10.0.22000.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.14701.20226
Host Executable: WINWORD.EXE

Description
Language inspection for assignment of LCase suggests usi