Hey all, I'm spending some time trying to update P...
# general
Hey all, I'm spending some time trying to update Pants at my company (it's become an annual-ish event for me), and am hitting this error while moving from 1.7.0 -> 1.8.0.
Copy code
==== stderr ====
Exception in thread "main" java.util.zip.ZipException: invalid entry size (expected 526140 but got 0 bytes)
I noticed this PR went into 1.8.0, which initially smells correlated: https://github.com/pantsbuild/pants/pull/5953 we do have a 3rdparty dependency on guava 20.0, is there more shading I should try and do? Can also provide more stacktrace/debug details in a gist. Thanks in advance!
does it repro on retry? that sortof looks like a bad cache fetch
Yep happens consistently
interesting. then possibly a corrupted cache entry...
possibly the input jar?
Hm I'll try without reading from cache
@busy-car-23170: i'm guessing that one of the input jars is truncated
you might try iterating through each of them and doing a check that they are valid... like
unzip -l $jar > /dev/null && echo $?
also, coursier has better validation of fetched artifacts, so maybe once you've made it onto a more recent version you can try that out?
All of the jars are unzippable 😕
Could it be that step is expecting a nailgun server for some I/O? We've turned off some usages of nailgun in a couple places
it does appear that the very final jar argument for that command does not exist, but I'm not sure what that is supposed to be (output perhaps?)
yea, that should be output.
nailgun shouldn't be necessary, afaik
might try wiping the ivy cache, and the caches under