Manu Sridharan

Ah, I see. You're probably looking to not see reports of initialization errors on such fields, yes? If so, that can easily be handled using the `-XepOpt:NullAway:ExcludedFieldAnnotations` option (see [here](https://github.com/uber/NullAway/wiki/Configuration)).

Yeah, for now you can handle this by passing `-XepOpt:NullAway:ExcludedFieldAnnotations=MonotonicNonNullDecl` as an Error Prone / javac argument. For CF compatibility we should probably bake in support for this annotation.

Now that #371 has landed, adding Reactor support should be *a lot* easier. In case anyone is interested 🙂

We may well not handle this case. We could fix, but my feeling is this comes up quite rarely. @spoerri what is your use case? On Sun, Sep 1, 2019...

@xenoterracide thanks for the report! I think the issue here is that the `after` parameter to the constructor is `@Nullable`, so doing `this.after = after` does not guarantee that the...

Agreed that if it comes up often enough, probably the stream nullability handler is where to add reasoning about this case.

/cc @lazaroclapp @subarnob

Another issue here: WALA seems to fail on JDK 11: ``` > Task :jar-infer:test-java-lib-jarinfer:jar FAILED Exception in thread "main" java.lang.IllegalStateException: could not find boot classpath at com.ibm.wala.util.PlatformUtil.getBootClassPathJars(PlatformUtil.java:62) at com.ibm.wala.properties.WalaProperties.getJ2SEJarFiles(WalaProperties.java:64) at...

Did some digging here around what it would take to support running JarInfer on JDK 11. There are two issues: 1. The WALA issue [from this comment](https://github.com/uber/NullAway/issues/259#issuecomment-443785457) is due to...

@lazaroclapp thoughts here?