1 files were completely excluded from scanning due to a fundamental problem that is known to cause problems scanning other files.

Open
#2,258 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, java, typescript
Domain
ci-cd, security

Research direction

Start with the linked Perform CodeQL Analysis workflow run and its warning, then trace how the CodeQL action reports Java files excluded because of module declarations. Done means the warning identifies the affected file or files and clarifies the module-info.java distinction without obscuring the existing analysis result.

Written by the indexing model from the issue text.

Description

I created a new test repository for setting up various github actions. The repository itself does not have real important code other than to demonstrate various things like a functioning build-pipeline even in case of module usage and such. The task I was given is to create releases to Maven Central on manual tags rather than to rely on the default release cycle.

While investigating into CodeQL action, I noticed that a warning is popping up during the Perform CodeQL Analysis step of the pipeline.

The exact message here reads as:

1 broken classes filtered out (1 result)
    * 1 files were completely excluded from scanning due to a fundamental problem that is known to cause problems scanning other files. Presently these are `module` declarations in a file not named `module-info.java`.

The warning is not really helpful at all as I can't really determine which file it is referring to even though this repo only has a handful of files. Not sure how much of an effort it would be to at least list the files that CodeQL is complaining about would be a sane thing IMO. The reported problem seems also a bit strange as there is a module-info.java file that declares a Java module. Which other file should there be that "declares" a module but is not within a module-info-java file?

Dominant language
TypeScript
Stars
1.6k
Forks
493
Avg merge
1d 13h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/codeql-action

All issues in github/codeql-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.