[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=507589&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-507589
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Nov/20 10:40
Start Date: 04/Nov/20 10:40
Worklog Time Spent: 10m
Work Description: jayendra13 edited a comment on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-721482691
We have fixed some of the modules, so I think creating a map somewhere
denoting modules fixed and not fixed would help for better tracking this issue.
What do you think? I am soon going to start this again.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 507589)
Time Spent: 11h (was: 10h 50m)
> [Umbrella] Eliminate nullability errors from Beam Java
> ------------------------------------------------------
>
> Key: BEAM-10402
> URL: https://issues.apache.org/jira/browse/BEAM-10402
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Priority: P1
> Labels: Clarified, starter
> Time Spent: 11h
> Remaining Estimate: 0h
>
> I enabled the checker framework and the core SDK exceeds 100 nullability
> errors immediately. We should make this number zero, since nullability errors
> are solved problem in computer science and they do periodically impact Beam.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
