[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=508194&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-508194
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Nov/20 17:10
Start Date: 05/Nov/20 17:10
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-722512670
Since there are 2000+ classes with issues, probably this is too many Jiras
and too much for a kanban? I don't know. Actually each class can be enough of a
challenge for a Jira. But maybe Jiras for the module level is easier to manage.
A spreadsheet containing the output of a bash script that finds the `TODO`
might make a lot of sense for tracking the burndown.
----------------------------------------------------------------
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: 508194)
Time Spent: 12h 20m (was: 12h 10m)
> [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: 12h 20m
> 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)
