[ 
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=507747&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-507747
 ]

ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Nov/20 19:43
            Start Date: 04/Nov/20 19:43
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-721936491


   > I think creating a map somewhere denoting modules fixed and not fixed 
would help for better tracking this issue
   
   Are you thinking something like a spreadsheet that we would keep up-to-date, 
or would this be a part of the build.
   
   With the change in https://github.com/apache/beam/pull/13191 we could 
identify fixed vs. not fixed classes and/or modules by grepping for 
`@SuppressWarnings("nullness") // 
TODO(https://issues.apache.org/jira/browse/BEAM-10402)`. Maybe that's enough 
for tracking? We could put a bash one-liner in the BEAM-10402 comments


----------------------------------------------------------------
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: 507747)
    Time Spent: 11h 10m  (was: 11h)

> [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 10m
>  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)

Reply via email to