Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U053HNE90>: I think the EOFException might be a red herring - I’ve seen those too and they seem like a fairly routine thing

```$ grep EOFException .pants.d/ng/*/stderr
.pants.d/ng/Checkstyle_compile_checkstyle/stderr:java.io.EOFException
.pants.d/ng/IvyResolve_resolve_ivy/stderr:java.io.EOFException
.pants.d/ng/JmakeCompile/stderr:java.io.EOFException```

```$ grep EOFException .pants.d/ng/*/stderr
.pants.d/ng/BootstrapJvmTools_bootstrap_bootstrap_jvm_tools/stderr:java.io.EOFException
.pants.d/ng/IvyResolve_resolve_ivy/stderr:java.io.EOFException
.pants.d/ng/PersistedSchemaCompatibilityChecker_gen_persisted_schema_check/stderr:java.io.EOFException
.pants.d/ng/ScroogeGen_gen_scrooge/stderr:java.io.EOFException
.pants.d/ng/ThriftLinter_gen_thrift_linter/stderr:java.io.EOFException``` etc

I think it's a deadlock in our compiler plugins

er, wait... not sure that makes sense... a single compiler instance isn't

The plugin reads in, potentially modifies, and writes out a file to disk.  This was not an issue when scalac invocations were serial

Then we noticed that file getting randomly clobbered in isolated

i think you'll want to have that file be distinct per output directory

it'll get picked up as an "untracked resource", and included in the artifact