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

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

                Author: ASF GitHub Bot
            Created on: 23/Oct/20 22:14
            Start Date: 23/Oct/20 22:14
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-715613311


   I'm not saying there isn't a problem with this PR, but this setup is 
strange. The command `./gradlew pullLicenses` essentially is doing a full build 
as part of that single task, and the two builds do not coordinate so they can 
clobber/corrupt files. Suspect that this PR just changes the timings so that it 
happens reliably. Filed https://issues.apache.org/jira/browse/BEAM-11116 and I 
will see if I can resolve it. So far, the commands run by the script don't seem 
to work as expected anyhow...


----------------------------------------------------------------
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: 504346)
    Time Spent: 6h 20m  (was: 6h 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: 6h 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)

Reply via email to