krakowski commented on pull request #13622: URL: https://github.com/apache/beam/pull/13622#issuecomment-752471261
I removed the custom annotation and replaced it with `org.apache.avro.reflect.Nullable`. I also refactored the methods responsible for checking if a `@Nullable` annotation is present (e.g [here](https://github.com/apache/beam/pull/13622/files#diff-beba37fb866fda6032626b6e228d47968f6ff0fee229246061d1fb96b04355cbR192-R198)). I didn't really know where to put the comment, so I placed it [on top of the test method](https://github.com/apache/beam/pull/13622/files#diff-404854b8f39406bdf5683ce4ae69f4ca4d055a40511e5c8208aeee9d4fd6ee0aR222-R234) as a javadoc. It looks like I ran into some kind of race condition by force pushing twice in a row since the Dataflow check is failing because of a locking problem. > Cannot lock Java compile cache (/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Examples_Dataflow_Java11_Commit/src/.gradle/6.7.1/javaCompile) as it has already been locked by this process. Is it possible to rerun this check? ---------------------------------------------------------------- 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]
