linter

~/code/rubocop$ grep -iro "autocorrect" . | wc -l
    1971
~/code/rubocop$ grep -iro "auto-correct" . | wc -l
    1551

Both autocorrect and auto-correct are used frequently in RuboCop. Should we be consistent? If so, which one?

Any change should only affect comments and other string content, not method names.

Your feature request related to a problem? Please describe.

GoKart is a new stand-alone security-focused static analysis tool.

Describe the solution you'd like.

Add support for GoKart. It uses go/analysis.

Describe alternatives you've considered.

Run GoKart separately to golangci-lint.

Additional context.

_No respo

What is the problem you're trying to solve?

I guess that selector-max-universal is performance related rule.
I.e. it is supposed to forbid patterns that hit perfomance.

Consider the following patterns (with selector-max-universal = 1):

1. "*" involves O(N) search. So, it is Good.
2. "* *" involves O(N^2) search. So, it is Bad.
3. "* + *" involves O(N) search ("+ *" = next element = it

Describe the bug

git diff-tree used by linter on push checks only files from the last commit and regardless of files status, so deleted or renamed files are also checked.

There are now 2 different git commands used for finding the list of broken files (find them here: https://github.com/github/super-linter/blob/v3.14.4/lib/functions/buildFileList.sh#L59-L105). git diff-tree is u

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

Expected Behavior

When an exception is thrown while running a Rule we should provide information about the file and the Rule.

Current Behavior

We only provide information about the file.

Context

We had some issues lately where the users report exceptions on a Rule but we need to ask for the full stacktrace to know what's going on (an example: #4612). And the issue is also "de

Is your feature request related to a problem? Please describe.
I want to be able to disable a whole level of violation. For example the low error level i want to disable but still run the checks on medium, high, critical.

Describe the solution you'd like
I would like to have this possible with a simple flag in the ci to do this. To disable the violation level : low, etc. that when yo

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

Current problem

Pylint check dictionaries for duplicates, but not sets.

DICTIONARY = {
    1: 2,
    2: 3,
    1: 2,  # duplicate flagged
}

SET = {
    1,
    2,
    1,  # duplicate not flagged
}

Desired solution

Flag duplicate set entries just as with dictionaries.

Additional context

No response

Affects PMD Version:
6.17

Rule:
All rulesets.

Description:
PMD output does not inform the user as to the number of rules contravened while running the tool. The user has to look at the output file.

Code Sample demonstrating the issue:

Sep 01, 2019 9:42:45 AM net.sourceforge.pmd.cache.FileAnalysisCache loadFromFile
INFO: Analysis cache loaded
Sep 01, 2019 9:

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.