oh, sorry, i asked my original question wrong, i should have said fetching ivy dependencies — compiling is irrelevant here, you’re right 🙂

will look again

then that is likely to be network bound

more precisely, round-trip bound.

reminder to use/share an artifact cache, as ivy lookups are cached

A simple method is to use the strict ivy conflict manager, which will cause the jar resolution to fail with an error if it detects two artifacts with conflicting versions. This has the advantage of forcing a dev to be aware of (and make a decision about) confliction versions.

the problem i found with this is that the version of zinc that pants uses (and which i think is the latest?) uses scala_2.10 (and thus org.scala-lang.scala-library@2.10), and didn’t seem to respect managed_dependencies. is that a misconfiguration on my end, or an actual issue?

Hello! New Pants user here and loving it so far. Thanks for the great project!

A couple of questions...

1. when I set

worker_count > 0

for

compile.zinc

, I get this error in nailgun:

compile(interval-util:all) failed: Problem launching via NailgunClient(host=u'127.0.0.1', port=59163, workdir='/Users/jack/Development/3sumo') command org.pantsbuild.zinc.Main -log-level info -analysis-cache /Users/jack/Development/3sumo/.pants.d/compile/zinc/252d64521cf9/interval-util.all/current/interval-util.all.analysis -classpath 
...
Problem in nailgun protocol with nailgun server at 127.0.0.1:59163: TruncatedHeaderError(u"Failed to read nailgun chunk header (TruncatedRead(u'Expected 5 bytes before socket shutdown, instead received 0',)).",)

but things work with

work_count = 1

. Are there any known issues with this?

2. for

dep-usage

, is there an intuitive explanation for

cost_transitive

? or some general thresholds for what's good/bad?

@fancy-rainbow-17651 : the default is for worker_count to be equal to the CPU count... are you sure you need to adjust it?

@fancy-rainbow-17651 : re: 2: the cost_transitive is just transitive line count. unfortunately, it's not deduped, so it probably overcounts

wouldn't be too hard to fix if you have time!

Ah ok, I started with a config from one of the open source twitter projects. Let me see if it works with

worker_count

removed.

@fancy-rainbow-17651 : what version are you using?

(of pants)

1.2.0

ok, that should be fine. although 1.2.1 is out

cool, will try that too

with the

worker_count

removed, I am still seeing the same error.

@fancy-rainbow-17651 : it sounds like nailgun is crashing for some reason. are you passing any additional options in

[compile.zinc]

?

@User uploaded a file: this is the config:

it does not work in containers

just in case this is in a CI or something

Pants disables nailgun in Travis

for example

Ah no, i am doing this on a laptop. No containers.

from http://www.pantsbuild.org/tshoot.html : "If nailguns stop resonding, look for clues in the stdout and stderr files in .pants.d/ng/*/*."

anything there interesting?