TheNeuralBit commented on pull request #13134: URL: https://github.com/apache/beam/pull/13134#issuecomment-721936491
> I think creating a map somewhere denoting modules fixed and not fixed would help for better tracking this issue Are you thinking something like a spreadsheet that we would keep up-to-date, or would this be a part of the build. With the change in https://github.com/apache/beam/pull/13191 we could identify fixed vs. not fixed classes and/or modules by grepping for `@SuppressWarnings("nullness") // TODO(https://issues.apache.org/jira/browse/BEAM-10402)`. Maybe that's enough for tracking? We could put a bash one-liner in the BEAM-10402 comments ---------------------------------------------------------------- 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]
