code-analysis

Affects PMD Version: 6.30.0-SNAPSHOT

Rule: UselessOverridingMethod

Description:

From pmd/pmd#2871 (comment)

Note: There seems to be a difference when having the class in the auxclasspath or not (typeresolution).

Code Sample demonstrating the issue:

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

[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.

Description

BeanUtils is a library that is doing automatic mapping to Java object.
It can cause arm when the attack controls part of the list of properties being sets. BeanUtils does not blacklist properties like class, classloader or other objects that are likely to load arbitrary classes and possibly run code.

Code

import org.apache.commons.beanutils.BeanUtils;

public

@MartinWitt points out rightly that assertTrue assertions should always have a message, see INRIA/spoon#4298 (review)

It's a good Spoon exercise to write a processor to detect assertTrue without messages.

We welcome first contributors to Spoon who add missing messages to assertTrue.

Environment data

VS Code version: 1.34.0
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: Ubuntu 19.04
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used: virtualenv

Problem

The type hints in the stub file for the current module aren't used for autocompletion.

I have a foo.pyi file as

I want to report a bug.

prefer-single-boolean-return warns on cases like the following:

function f() {
  if (condition) {
    return true;
  } else {
    return false;
  }
}

However, this control flow is arguably unidiomatic JS regardless of whether it's returning a boolean. These cases are already warned against by eslint's built-in [no-else-return](https://esli