java/local-shadows-field: a local declared inside a lambda or anonymous class body is not reported

Abierto
#22,969 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java
Área
devtools

Línea de trabajo

The likely cause is the shadows predicate in Shadowing.qll, which requires the local's callable to be declared by the class that owns the field (method.getDeclaringType() = c). Start by running the three samples (ShadowSeed, ShadowVariant, ShadowControl) against java/local-shadows-field and confirming only the seed fires. Done when the local inside the lambda and inside the anonymous class is reported, and the seed case still is.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Java

Description of the issue

The query reports the local String[] arr in ShadowSeed.getArr(), which has the same name as the field the method reads as this.arr. Declare the same local inside a lambda in that method (ShadowVariant) or inside an anonymous class (ShadowControl) and nothing is reported, though it still shadows the field and the method still reads this.arr.

Probably the shadows predicate in Shadowing.qll: it requires the local's callable to be declared by the class that declares the field (method.getDeclaringType() = c). Inside a lambda the callable is the lambda's own method, and inside an anonymous class it's that class's method.

Query: java/local-shadows-field (codeql/java-queries 1.1.10)

CodeQL CLI: 2.27.2

Code samples

seed/ShadowSeed.java:

public class ShadowSeed {
    String[] arr;
    String[] getArr() {
        String[] arr;                      // shadows the field; the query fires here
        return this.arr;
    }
}

variant/ShadowVariant.java:

public class ShadowVariant {
    String[] arr;
    String[] getArr() {
        Runnable r = () -> {
            String[] arr;                  // the same local inside a lambda body; not reported
        };
        r.run();
        return this.arr;
    }
}

control/ShadowControl.java:

public class ShadowControl {
    String[] arr;
    String[] getArr() {
        Runnable r = new Runnable() {
            public void run() {
                String[] arr;              // inside an anonymous class; not reported either
            }
        };
        r.run();
        return this.arr;
    }
}

How to reproduce

codeql database create db --language=java --build-mode=none \
    --source-root=<one directory> --overwrite
codeql database analyze db \
    codeql/java-queries:codeql-suites/java-security-and-quality.qls \
    --format=csv --output=out.csv
# one database per directory

Expected result

"Potentially confusing name: method ... also refers to field arr (as this.arr)" on the local in ShadowVariant.java (line 5) and in ShadowControl.java (line 6), as on ShadowSeed.java (line 4).

Output of the commands above:

### CodeQL 2.27.2  query: java/local-shadows-field
### suite: java-security-and-quality.qls, --build-mode=none, per-file isolated databases
### extraction JDK: openjdk version "21.0.11" 2026-04-21 LTS

--- SEED -- expected: query fires (seed/)
"Possible confusion of local and field","A method in which a variable is declared with the same name as a fiel

--- VARIANT -- expected: query fires, actual: not reported (the bug) (variant/)
    (query reported nothing)

--- CONTROL -- the same construct in an anonymous class, expected: query fires (control/)
    (query reported nothing)
Lenguaje dominante
CodeQL
Estrellas
10.3k
Forks
2.1k
Merge medio
2 d 6 h
PR fusionados (30 d)
137

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/codeql

Todos los issues de github/codeql

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.