if you want to "show all the warnings for everything", use the former... if you want to just see warnings for a particular target, make a whitespace change or something and then use the latter (which will cause only that target to be built)

(and, to be clear: the artifact cache is located elsewhere:

.cache

by default)

thanks for all the info, @witty-crayon-22786!

yep,

--cache-compile-zinc-ignore

does what I want 🙂

how do you configure that option?

@eager-raincoat-57702: generally on the command line.

although all of pants' options can be specified on the command line, as environment variables, or in pants.ini/pantsrc files

i think i tried every valid option but just am on an old version of pants 😁

yea.

--cache-compile-zinc-ignore

was added in 1.4.0dev something.

--no-cache-compile-zinc-read

has existed for a long time.

the way to get equivalent behaviour would be to run

./pants clean-all

and then build with

--no-cache-compile-zinc-read

thanks

working on upgrading to newer pants right now anyway

Hi, we're trying to use pants v1.3.1rc0 for compatibility with Mac OS 10.13, but getting the following error:

Exception message: Failed to fetch binary bin/native-engine/mac/10.13/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so from any source: (Failed to fetch binary from <https://s3.amazonaws.com/binaries.pantsbuild.org/bin/native-engine/mac/10.13/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so>: Fetch of <https://s3.amazonaws.com/binaries.pantsbuild.org/bin/native-engine/mac/10.13/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so> failed with status code 404)

I guess there's some missing overlap between https://github.com/pantsbuild/pants/pull/4894 and https://github.com/pantsbuild/pants/pull/4806. What's the best way to resolve this issue?

The workaround is noted in the issue associated with https://github.com/pantsbuild/pants/pull/4894, but it's a bit buried. Try this pants.ini edit out: https://github.com/pantsbuild/pants/issues/4893#issuecomment-332019335

Unfortunately I still get a 404 looking for the 10.12 binaries

Exception message: Failed to fetch binary bin/native-engine/mac/10.12/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so from any source: (Failed to fetch binary from <https://s3.amazonaws.com/binaries.pantsbuild.org/bin/native-engine/mac/10.12/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so>: Fetch of <https://s3.amazonaws.com/binaries.pantsbuild.org/bin/native-engine/mac/10.12/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so> failed with status code 404)

Ok. I'm on my way into the office but will look into this within the hour.

Thanks!

@dazzling-plumber-90795 this should now be fixed:

$ curl -sSL <https://binaries.pantsbuild.org/> | xmllint --format - | grep ab51a617f069641eb6b47e8713e51150ad0a6ab0
    <Key>bin/native-engine/linux/x86_64/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.10/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.11/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.12/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.13/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.7/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.8/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>
    <Key>bin/native-engine/mac/10.9/ab51a617f069641eb6b47e8713e51150ad0a6ab0/native_engine.so</Key>

Filed https://github.com/pantsbuild/pants/issues/5061 to track a general fix for 1.3.X, releases of which which will continually run into this issue if left as-is.

confirmed this works

thanks a lot for the help

You're welcome.

Hi pants gurus! I would love to get some discussion going on this PR: https://github.com/pantsbuild/pants/pull/5050

It's super useful, especially when working on cross-version support for Python projects, to be able to control the behavior of coverage.py

At the next Pants major release version, BUILD files won't support arbitrary python code, they'll be purely declarative. So avoiding code if at all possible will help you in the long run.

you said @enough-analyst-54434 - and Kderr asked

That include passing dictionary literals as arguments to targets?

I had the same question when you have time 🙂

Literals - in some form - will be supported. Whether that's a python dict literal or a json object literal - unclear at this point. If we were to switch from python syntax though we'd likely provide a migration tool.

So, today you

java_library(**{'key': 'value', ...})

?

We are doing something like this:

custom_target(
  name=‘test1’,
  tags=[‘foobar’],
  extra_vars={
   ‘foo’: ‘bar',
   ‘baz’: {
      ‘baz’: ‘faz’,
      'ref': ‘1234’,
      'port': 4567
    }
  },
  dependencies=[
    ‘dep1/foo,
    ‘dep2/bar’
  ]
)

Thanks for the answer john.sirois - that sounds good.