[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=506396&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-506396
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/20 20:41
Start Date: 29/Oct/20 20:41
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-719008995
Here are some samples of runs against commits and phrases:
- https://scans.gradle.com/s/acfajsh5mnxj2/timeline?sort=longest
- https://scans.gradle.com/s/wbqztstpu7pdo/timeline?sort=longest
- https://scans.gradle.com/s/7qqcuygtqlaou/timeline?sort=longest
It is hard to determine the real likely slowdown in practice. The tasks that
were the longest and most problematic in the bad run are almost always
`FROM-CACHE`.
----------------------------------------------------------------
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: 506396)
Time Spent: 10.5h (was: 10h 20m)
> [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: 10.5h
> 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)
