The Wayback Machine - https://web.archive.org/web/20220708222104/https://github.com/topics/static-code-analysis
Skip to content
#

static-code-analysis

Here are 434 public repositories matching this topic...

kassi
kassi commented Dec 14, 2020

The example in the documentation for Style/GuardClause is misleading because mentioned bad and good version don#t match execution.

It says

# bad
if something
  foo || raise('exception')
else
  ok
end

# good
foo || raise('exception') if something
ok

However both versions behave differently and bad can't be replaced by good.

Imagine something being true and `f

documentation good first issue
semgrep
erwanlr
erwanlr commented Jun 22, 2022

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
enhancement good first issue priority:medium
datree
noaabarki
noaabarki commented Feb 24, 2022

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

enhancement good first issue up for grabs
reviewdog
davidak
davidak commented Jun 18, 2018

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

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

Expected behavior
working as described in readme

Bandit version

ba
bug good first issue
harupy
harupy commented Jul 4, 2022

Bug description

from abc import abstractmethod, ABCMeta


class WildAnimal(metaclass=ABCMeta):
    @abstractmethod
    def make_sound(self):
        pass


class Panther(WildAnimal):
    def make_sound(self):
        raise NotImplementedError("Panther")


class PantherChild(Panther):
    pass

pylint raise the following error against the code above?

Good first issue Documentation 📗 Needs PR
aaronmorris
aaronmorris commented Mar 28, 2022

Affects PMD Version: 6.42.0

Rule: ApexCRUDViolation

Description:
I'm getting the "Validate CRUD permission before SOQL/DML operation" error when updating a list of a custom object, but not on the individual.

Code Sample demonstrating the issue:

public static CustomObject__c updateCu
good first issue a:false-positive
revive
zimmski
zimmski commented Apr 7, 2022

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

When one is using the method "WriteString" of the type "strings::Builder" and does not handle the error it is flagged because all errors must be handled. However, This method never returns an error. Hence, it makes sense to ignore it (even by default).

The problem with revive is, that it does not allow to ignore methods with

msridhar
msridhar commented Jan 22, 2022

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

Fernal73
Fernal73 commented Nov 2, 2021
[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.
FullValueRider
FullValueRider commented Dec 10, 2021

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

bug enhancement feature-inspections up-for-grabs

Improve this page

Add a description, image, and links to the static-code-analysis topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the static-code-analysis topic, visit your repo's landing page and select "manage topics."

Learn more