[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=534476&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-534476
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Jan/21 19:29
Start Date: 11/Jan/21 19:29
Worklog Time Spent: 10m
Work Description: je-ik commented on pull request #13719:
URL: https://github.com/apache/beam/pull/13719#issuecomment-758172396
None that I'm aware of. I was just trying to legalize the current state. I
changed the fix not to return null, which is really probably better, as it
seems there is code that could throw NPE when subTriggers() return null.
----------------------------------------------------------------
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: 534476)
Time Spent: 14h 10m (was: 14h)
> [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: 14h 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)
