Is there a way to reuse a variable in several BUILD times?

Hi there, I'm gonna give pants 2.0 a try. Looking forward to it, thanks for making this open source!

Is there anything I should look out for for when using the 2.0.0dev6 version?

Hey I’m trying to integrate the

isort

backend using v2 with pants version

1.30.0

. Is there a way for

isort

to know about 3rdparty dependencies? In order to sort them into a separate section from buildins and first-party files. Normally I believe it looks at the environment to tell if something came from pip. I’m not sure how to do this in pants. I’ve declared the dependencies in a file

3rdparty/requirements.txt

and invoking

python_requirements()

Isn't it odd that after switching from ivy to coursier on my scala project I get different set of jar dependencies included in my fat jar via

./pants binary

? (judging by debug messages here https://github.com/pantsbuild/pants/blob/1.29.x/src/python/pants/backend/jvm/tasks/jvm_binary_task.py#L105 ) Any possible explanation / ideas for debugging this?

I see there was conversation a few month back about using a WSGI or ASGI worker as your entry_point, is there an example of this working if it is? For example:

gunicorn main:app

(Pants 2.0)

And does Pants have any support for building docker images?

Are there plans to support Pants on ARM? And, somewhat related to that, is there support for cross compilation (building for ARM on x86)?

We use Sphinx for our documentation. In our monorepo, we have a sources directory that has the main site, but it also digs into sources directory for each project along with getting module doc strings for every project's code. We created a

pants-plugin

for building project's docs called

makedocs

. When we run

./pants makedocs ${target}:docs

it builds the docs for that target. This plugin needs to know where the main config file is for the repo. Right now we do some path magic and figure out where the ROOT of the monorepo is located on the filesystem and then hardcode the path to the main

conf.py

file and the output directory. This works in 1.18 but breaks in >1.25. What is the 👖 way to solve this problem? Do I get more sophisticated in finding the path to the ROOT of the monorepo (this feels like something

./pants

should know)? Or do I go whole hog with the chroot and add the main

conf.py

as a resource for every project's

makedocs

target (did I mention the plugin defines a target type?). The latter solution seems like it will be wasteful in that when we build the whole site with every module, we will be copying the whole monorepo into the chroot. The former is what I am leaning towards, but then I have to work around the chroot. Any suggestions would be apprewciated

In the docs online, the following is stated for CI:

Directories to cache
In your CI's config file, we recommend caching these directories:

$HOME/.cache/pants/setup: the initial bootstrapping of Pants.
$HOME/.cache/pants/named_caches: caches of tools like pip and PEX.
$HOME/.cache/pants/lmdb_store: cached content for prior Pants runs.

version 1.26 does not appear in the list of versions on the docs. Does the above statement still hold true for 1.26?

Hey , when is the 2.0.0.dev7 release planned?

Hi, i have an issue trying to build a project behind a coorporate proxz:

Engine traceback: in Create PEX Traceback (no traceback): <pants native internals> Exception: Error downloading file: error sending request for url (https://github.com/pantsbuild/pex/releases/download/v2.1.11/pex): error trying to connect: invalid certificate: UnknownIssuer Traceback (most recent call last): File "/home/mafunk/.cache/pants/setup/bootstrap-Linux-x86_64/1.29.0_py37/lib/python3.7/site-packages/pants/bin/local_pants_runner.py", line 356, in run engine_result = self._maybe_run_v2(v2) File "/home/mafunk/.cache/pants/setup/bootstrap-Linux-x86_64/1.29.0_py37/lib/python3.7/site-packages/pants/bin/local_pants_runner.py", line 236, in _maybe_run_v2 return self._maybe_run_v2_body(goals, poll=False) File "/home/mafunk/.cache/pants/setup/bootstrap-Linux-x86_64/1.29.0_py37/lib/python3.7/site-packages/pants/bin/local_pants_runner.py", line 260, in _maybe_run_v2_body poll_delay=(0.1 if poll else None), File "/home/mafunk/.cache/pants/setup/bootstrap-Linux-x86_64/1.29.0_py37/lib/python3.7/site-packages/pants/init/engine_initializer.py", line 256, in run_goal_rules goal_product, params, poll=poll, poll_delay=poll_delay File "/home/mafunk/.cache/pants/setup/bootstrap-Linux-x86_64/1.29.0_py37/lib/python3.7/site-packages/pants/engine/internals/scheduler.py", line 614, in run_goal_rule self._raise_on_error([t for _, t in throws]) File "/home/mafunk/.cache/pants/setup/bootstrap-Linux-x86_64/1.29.0_py37/lib/python3.7/site-packages/pants/engine/internals/scheduler.py", line 578, in _raise_on_error wrapped_exceptions=tuple(t.exc for t in throws), pants.engine.internals.scheduler.ExecutionError: 1 Exception encountered:

I am running with: export PYTHON=/usr/bin/python3.7; export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt; ./pants binary src/python:: --print-exception-stacktrace -ldebug

Hope this is right place to ask this question

Thanks for the 2.0.0.dev7 release. There is a minor bug , that I found and not sure whether it exists in prior dev releases of 2.0.0. The issue is, when having an entrypoint that points to a no-arg function in a module (entrypoint=helloworld.main:say_hello), ./pants run ${python_binary_target_address} fails. But I can build the PEX file using ./pants binary ${python_binary_target_address} and run it using ./dist/pex_file.pex. There is a workaround, so it is not a big issue but wanted to highlight it as I came across it.

I don't know if this is just me not understanding how to use it or if there is an issue with the run goal and pantsd, but when I run any long running python binary target withh pantsd enabled, I can't seem to stop the execution. SIGINT and SIGQUIT (Ctrl+C, Ctrl+\) produce a log message, but actually don't seem to terminate the running python process. This is v1.30.0 btw. Does anyone else have a similar issue?

Hi guys I´m trying to debug OOM issues when running my unit tests. I’ve configured

pants.ini

to increase heap size as such:

[DEFAULT]
pants_version: 1.17.0
jvm_options: ["-Xmx4g"]

[test.junit]
jvm_options: ["-Xmx4g"]

but whenever I profile the testRunner using VisualVM it tells me that the max heap size is

-Xmx256m

, how can I increase the heap size for the testRunner?

did you try using

[jvm.test.junit]

as group?

e.g. this is what we have in our pants.ini:

[jvm.test.junit]
options:[
    "-Djava.awt.headless=true", "-Duser.language=en", "-Xmx1g"
  ]

that worked! Thanks alot!

Thanks for the tip @plain-river-51682!

Is the

lmdb_store

supposed to be used at all when running pants v1 engine?

yes! the v2 engine is used to implement several parts of the v1 interface under the hood

source files will always be snapshotted by traversing directories in parallel with rust code for example

Got it, thanks 👍

let us know if you see anything that seems weird!

https://twitter.com/pantsbuild/status/1294342027530792960 Python people! Do your (unit) tests tend to live in the same directory as the thing they test, or a different directory? #python #monorepo Twitter

Hi, today we experienced a couple of issues where pants wasn't able to find gcc (required by one 3rd party dependency) when preparing the pex. We got it working adding

/usr/bin

to

interpreter_search_paths

I suspect it's not using the correct PATH, have you ever seen this sort of issue?