[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=504008&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-504008
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Oct/20 04:43
Start Date: 23/Oct/20 04:43
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-714907209
OK. The commits look right to me. Let me know if it helps to split things
any other way. I had hoped this would be a pretty silly PR but it got slightly
involved. I would say two things to check are:
1. all except the monster commit make sense
2. the monster commit contains nothing other than suppressions
Yea?
----------------------------------------------------------------
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: 504008)
Time Spent: 4h 40m (was: 4.5h)
> [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: 4h 40m
> 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)
