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

Pants

the `java.io.EOFException` is almost certainly not related - the `TruncatedHeaderError` is likely just the nailgun dying w/ your debug printlns. a full paste of the pants invocation and its output would probably be helpful for context. usually there would be some more specific errors above the actual singular error message.

ok I modified zinc to dump the exception to stdout, it’s a NPE in the scala compiler

```                       TRACE:
                       java.lang.NullPointerException
                       	at scala.tools.nsc.typechecker.Typers$Typer.noExpectedType$1(Typers.scala:3464)
                       	at scala.tools.nsc.typechecker.Typers$Typer.scala$tools$nsc$typechecker$Typers$Typer$$handleMonomorphicCall$1(Typers.scala:3467)
                       	at scala.tools.nsc.typechecker.Typers$Typer.doTypedApply(Typers.scala:3495)
                       	at scala.tools.nsc.typechecker.Typers$Typer.tryNamesDefaults$1(Typers.scala:3381)
...```

so I’ll probably have some minor pants patches to dump better info in such a case

<@U0N6C2Q9F>: oo, that would be a welcome patch.

Thanks <@U0N6C2Q9F>! And hello :simple_smile:

Why are we not capturing that NPE in zinc’s output in the usual way?

is there a general purpose BUILD file generator for java code? or do most pants users have something in-house?

<@U051221NF>: the relevant code from `pants/src/scala/org/pantsbuild/zinc/Main.scala` is: ```      case e: Exception =&gt;
        if (isDebug) e.printStackTrace
        val message = e.getMessage
        if (message ne null) log.error(message)
        sys.exit(1)
```

the trace would only get dumped in -debug mode

it is unclear why I didn’t see the message in the error output

stderr when looking in pants server UI was empty

pants’s own debug level should be passed through to zinc though

isnt there also an issue with relative position in the cli args for -ldebug

for the most part, I was not running with -ldebug

yeah, if you would like me to do some testing, let me know

Well, you can do `./pants compile.zinc -ldebug`

To have the debug level only apply within compile.zinc

Or you can use `—compile-zinc-level=debug`

does pants pass its environment variables to zinc?

context: as I debug this compiler NPE, I need a side channel to pass scalac options to my custom zinc so it can add them to the scalaOptions without me triggering a rebuild of lots of targets