TIL that

@memoized_property

caches on the class level, with the instance as a key

I’ve lately been finding myself wanting a cleaning goal that doesn’t delete the logs and timing information. Is that something other folks have thought about?

Hi all, I upgrading an existing pants repo that has some python pex configuration that is dependent on binaries.path_by_id when creating cross-platform pex binaries. This section in the pants.ini config is removed post 1.6.x, so I was wondering if there is an alternative that I could use in order to build pex binaries on OS X to be run in Linux docker containers.

Hi pants people! Is there flag to force all the transitive dependencies to build/bundle? I have a build target

A

in a separate BUILD file from another target

B

.

A

depends on

B

.

A

is built via the

--changed-parent

flag, but `B`’s

/dist

artifacts aren’t available when

A

is triggered, because 1) We don’t cache

/dist

and 2) `B`’s distributable artifact is never built because the BUILD file is never invalidated.

see

./pants help-advanced changed

in particular:

--changed-include-dependees=transitive

is probably what you want

awesome! life saver!

thanks @witty-crayon-22786

Hmm, I sorta needed the other direction:

--changed-include-dependencies

. I think I have bigger questions now like should I depend on anything directly in dist or not? Or should I be caching the entire

/dist

folder. If I can force it in the opposite direction then I can force the artifacts to rebuild from the

.cache

. Now I’m starting to wonder if what’s in the cache is verbatim the dist artifact 🙂 I’ll probably dig into that, but I think I can also get out of this by caching the entire /dist folder right now.

ah, gotcha.

yea, bundle will only put the bundles for "roots" in

dist

.

rather than also for the transitive deps.

you could split your run into

./pants --changed... dependencies | xargs ./pants bundle

Nice. Mind = blown 🙂 Now it’s going all the way down to the python packages and throwing an error:

Unknown goals: apache-airflow[crypto]==1.9.0, psycopg2-binary==2.7.5, boto3==1.7.52

. If I can get past that I think it’s gold.

err I can grep the targets by

src/

for now 🙂

more fuel for the query language movement, i suppose

Hello. We just updated to 1.11.dev0 and running a jvm run task doesn't work. The error we get is:

Exception caught: (<type 'exceptions.TypeError'>)

Exception message: can only concatenate list (not "NoneType") to list

The root cause seems to be this commit: https://github.com/pantsbuild/pants/commit/71467604c5d43df6000995346f245f3768441c03 The target should default to

[]

(we don't use any extra jvm options) but it seems the

get_field_value

might be run on a wrong target here: https://github.com/pantsbuild/pants/commit/71467604c5d43df6000995346f245f3768441c03#diff-330c9a1c6b6b5df53b8e2eae2f383035R85 I get the required empty list if I change

target.payload....

to

binary.payload...

Is this diagnosis correct?

Hi, could you post your BUILD file, please?

Specifically, I would like to know if the failing target is a JvmApp, as I may have not tested that codepath, and would like to create a test for that.

it's a jvmapp

the branching for the jvmapp logic seems to be this

binary =

assignment

Yep

Cool, I’ll investigate and get a PR out asap, if you could copy-paste your initial comment into an issue it would be great

another workaround could be by adding a default value to

get_field_value

I'll open an issue

I thought it already did that, but apparently not. In either case, I’d like to have the JvmApp case covered. Thanks!

thanks for a quick response

Hello all, does anyone know why the following would happen?

$ ./pants --tag="something" filter 3rdparty/python:ansicolors
Exception caught: (<class 'pants.build_graph.address_lookup_error.AddressLookupError'>)

Exception message: Build graph construction failed: ResolveError "ansicolors" was not found in namespace "3rdparty/python". Did you mean one of:
  :ansicolors
  ...
  :requests
  :requirements.tx

It exists in the requirements file:

ag ansicolors 3rdparty/python/requirements.txt
7:ansicolors==1.1.8

I am getting this for any existing target with

filter

. Did filter change in 1.9.x?

Well, your asking to filter the given targets (just one) but excluding targets without a something tag, so confusing output aside, no such target exists.