Skip to content

Eliminate nullability errors from :sdks:java:core #20507

Open

Description

@damccorm

Just choose any file that starts with @SuppressWarnings("nullness") and eliminate the annotation and fix the errors!

As of 2020-07-20 setting -Xmaxerrs 10000 there are 1451 errors in the core Java SDK.

Imported from Jira BEAM-10496. Original Jira may contain additional context.
Reported by: kenn.
Subtask of issue #20497

Activity

  1. aditya-mistri commented on Feb 10, 2023

    @aditya-mistri

    please assign me this issue , I want to work on this issue

  2. damccorm commented on Feb 10, 2023

    @damccorm
    ContributorAuthor

    Hey @aditya-mistri you can self assign issues by commenting .take-issue. That will trigger a github action to assign you. It may take a little bit depending on load on actions

  3. HoussemNasri commented on Feb 18, 2023

    @HoussemNasri

    As Aditya didn't respond to taking the issue, I assume he is no longer interested.

  4. HoussemNasri commented on Feb 18, 2023

    @HoussemNasri

    .take-issue

  5. HoussemNasri commented on Feb 19, 2023

    @HoussemNasri

    Hey @damccorm, I built the project locally and everything seems to go fine, but I'm not sure where to put the enableChecker: true. As far as I understand, enableChecker should be passed to the beam gradle plugin. I have tried to pass it inside applyJavaNature closure but then loading gradle changes would fail. I also have tried to use enableSpotbugs instead, this time gradle reloads fine but compiling java files doesn't trigger the check to run.

    I did more research and stamped upon this PR #13134 which seems to enable the checker framework for all modules/classes and disable it for certain classes that match a certain pattern. I figured since the Jira ticket was opened before the PR then the issue might need an update.

  6. damccorm commented on Feb 21, 2023

    @damccorm
    ContributorAuthor

    @kennknowles do you have context here?

  7. kennknowles commented on Feb 21, 2023

    @kennknowles
    Member

    Ah, the description is obsolete. Checker framework is enabled in all modules now. We automatically added @SuppressWarnings("nullness") to every class that had nullness errors. To work on this issue, find a class that has @SuppressWarnings("nullness") and remove that, then fix the errors.

  8. kennknowles commented on Feb 21, 2023

    @kennknowles
    Member

    Since checkerframework is integrated into compilation, all you have to do to get the errors is recompile.

  9. nitinware commented on Sep 7, 2026

    @nitinware
    Contributor

    .take-issue

  10. nitinware commented on Sep 16, 2026

    @nitinware
    Contributor

    this issue can be closed, fix addressed in pr: #40046

  11. kennknowles commented on Sep 16, 2026

    @kennknowles
    Member

    I think there yet more suppressions to be eliminated. Thanks for what you've contributed so far, though!

  12. nitinware commented on Sep 17, 2026

    @nitinware
    Contributor

    Thanks @kennknowles, If you’re referring to #20497, I’ll take a look at the remaining nullness suppressions and work on addressing them.

  13. HoussemNasri commented on Sep 19, 2026

    @HoussemNasri

    .free-issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions