let me check

Oh, right, it's fixed in 2.8.1rc0

which is basically just 2.8.0 with that one fix, so it should be safe to upgrade to

Has anybody had experience running Pants on gitpod.io? I'm running into

ERROR: Can not perform a '--user' install. User site-packages are not visible in this virtualenv.

when I try to run anything (even

./pants version

)

This conversation got lost a bit in the run-up to the U.S. holiday, but please do contribute your thoughts on moving community chat from Slack to a search engine indexable forum with more archival storage. https://pantsbuild.slack.com/archives/C046T6T9U/p1637337695015300

Hiring? Feel free to post announcements here. No better place to find engineers who already use Pants in their workflow and embrace developer experience as a priority.

Is there an easy way to tell pants to ignore symlinks when doing

lint

. It seems black/isort end up turning the symlink into a copy of the file it links to if they are run on the file and need to make changes

We have some team members that do local development on their mac. When running docker packaging from mac, the build step will succeed but an incompatible pex_binary gets loaded into the built container -- which fails at runtime. This can be very confusing for beginners. This is basically the issue described here. I think the long term solution of allowing to build from a local docker context described here is a good one. However, in the meantime, it would be great if we could output an error at build time so people on the team (most of whom are using pants for the first time) can catch errors early on. Is there some simple way for me to hack this check into our pants build process? Maybe some sort of conditional check in the build file?

@hundreds-father-404 I’ve started using

./pants update-build-files --check

and get these rather verbose info lines:

18:29:02.26 [INFO] No required changes to BUILD files found. However, there may still be deprecations that `update-build-files` doesn't know how to fix. See <https://www.pantsbuild.org/v2.9/docs/upgrade-tips> for upgrade tips.

What do you think about including the “… However, there may still be…” part only when not running in check mode?

How do I expose a port with

./pants run src/docker/Dockerfile

?

Is there any way to see

./pants filedeps

output as a graph?

Any way to make a python source target and all of its transitive internal dependencies available to a docker image?

pants tailor

isn’t generating some build files I would have expected it to (there are

.py

files in the directory). Is there a readable explanation of the logic of how tailor decides where a

BUILD

file is needed that someone can point me at?

🤔 Is there a way to set

local_store_dir

and

named_caches_dir

via environment variables?

Posting this not for help, but for visibility for anybody who runs into this in the future and searches for this: I recently ran into this after a `./pants package`:

14:52:58.47 [ERROR] 1 Exception encountered:

  ValueError: Error writing file /home/wimax/src/grapl/dist/analyzer-executor.pex: Os { code: 14, kind: Uncategorized, message: "Bad address" }

14 is an EFAULT, so, bad pointer Nuking ~/.cache/pants fixed the problem 🤷‍♂️

are the default source patterns extensible globally? I want to make

factories.py

globally a

python_test_util

and not a

python_source

maybe something like

[default-sources]
python_sources += ['!factories.py']
python_test_utils += ['factories.py']

and if not, is this easily done via a plugin?

My pants deamon is dying frequently with the following message. Every time I run the package goal and others.

23:31:28.31 [ERROR] saw filesystem changes covered by invalidation globs: content changed (Digest('d4cd7349f655cdec6b7205d5639dc60a2c0bb7b23c9c63e60abc9ac129b3abae', 337) fs Digest('c02add6f83006535b9c4d0382501f86a486283419549edd02e97906b04d0a28a', 337)). terminating the daemon.
23:31:28.49 [ERROR] service failure for <pants.pantsd.service.scheduler_service.SchedulerService object at 0x7f498aef4fd0>.

Any tips on figuring out what files are actually causing the digest to change? In the case where just the digest and not the fileset changes it doesn't look like the culprits aren't even calculated: https://github.com/pantsbuild/pants/blob/e70071244c20cd377c88bcbf87c4a6b0ec7d68b4/src/python/pants/pantsd/service/scheduler_service.py#L109 It looks like the invalidation glob could potentially be large: https://github.com/pantsbuild/pants/blob/e70071244c20cd377c88bcbf87c4a6b0ec7d68b4/src/python/pants/option/global_options.py#L1540

Is it possible to define rules for the

./pants tailor

command? Like, I have

.vue

and

.js

files, and I want those directories to be populated with

BUILD

as well

Some people on my team are asking about the performance implications of pex files (as opposed to more traditional directory structures). Are there any benchmarks or other resources I can point them at?

Pants is the Open Source Project of the Week on SD Times! https://sdtimes.com/softwaredev/sd-times-open-source-project-of-the-week-pants/

I know this is quite new but will pants be looking into using

Pyoxidizer

https://github.com/indygreg/PyOxidizer

Hi, I'm on pants 1.27.0 building scala with local cache (read/write) + s3 cache (read only from laptop, its written from CI). I notice things get slow with rsc compiler at this callstack.

sbt.internal.inc.Incremental$.prune

seems like its looking in

.pants.d/**

to clear out old things? I switch branches a lot so its quite big (

incremental_caching=False

also, I think we had problems):

$> du -sh .pants.d/compile
5.3G	.pants.d/compile
$> du -sh .pants.d/local_artifact_cache
2.7G	.pants.d/local_artifact_cache

Is there anyway to disable that pruning? I already set

max_entries_per_target

to a big number (well actually, I modified the code so it doesnt even do the pruning, then I clean it in a cron daily), but this seems like a different prune controlled by zinc? Any ideas how I can skip this one too?

what targets do people test before a deployment to an environment? All of them, changed targets since last deployment, changed targets since

HEAD^

?

Hey! we have a Python repository where Pants could help us quite a but, but we are struggling to come up with the right usage given our (complex) repository structure. In abstract terms the repository looks like this:

src/
   plugins/foo/schema.py
   plugins/bar/schema.py
   plugin_registry.py
   webserver.py
test/
   plugins/foo/test_foo.py
   plugins/bar/test_bar.py

The challenge is that

plugin_registry.py

is loading those plugins dynamically using

importlib

. Any usage of a plugin goes through the registry as a facade. In practice this means that there is no import of

foo/schema.py

in

test_foo.py

but we only import the registry and have it load the right plugin for us. In some integration tests it gets even more complicated. The registry and plugins are loaded in another process and the tests only call a REST API, without any import of registry or plugins in the test code. This usage does not play well with the pants auto-discovery of Python import dependencies. We can think of two ways out of this, but both have their downside (see thread). Is there any option we have missed? I am curious if you have further ideas for us

I'm unable to run

./pants check ::

, it keeps trying to resolve the constraints forever. I use a private pypi, and the env variable

PANTS_PYTHON_REPOS_INDEXES

. Besides that I don't do anything else. What am I missing?

Howdy all, Bringing a discussion I’ve already run past a few maintainers into public view: I think we should consider adopting Pantsbuild as one of the acceptable names for Pants. I’ll post further discussion in the thread below, and would love to hear thoughts from the broader Pants(build) community!

How do I pass a secret to when building? I have this `Dockerfile`:

FROM python:3.8
...
COPY n20-*.whl .

RUN --mount=type=secret,id=pipconfig,dst=/etc/pip.conf \
    python -m pip install --no-cache-dir n20-*.whl

With this `BUILD`:

docker_image(
    name="n20",
    dependencies=["src/python/n20:wheel"],
    image_tags=["{build_args.BITBUCKET_BUILD_NUMBER}"],
    extra_build_args=["--secret id=pipconfig,src=pip.conf"],
    repository="recital/n20-dev",
)

The

pip.conf

is actually not there. Do I need to have a

file()

with

pip.conf

? If so, how exactly? Because I added that and it didn't work as well.

Is it possible to define

resource

target using a directory which has multiple directories inside it? In general, whatever examples I see in docs are using single or multiple files, but hardly with directories.

What context does pants uses when building docker images? In this case I have a BUILD file inside the

src/pyfleet-vehicle-spec

with this target.

docker_image(
    name="docker_dev",
    source="Dockerfile_dev"
)

This is a dockerfile where I am adding a

requirements.txt

FROM python:3.8.1-slim
COPY requirements.txt /usr/src/app

When I run

./pants package <path_to_docker_file>

, it can't find the file inside the

src/pyfleet-vehicle-spec

. This is the error stack

./pants package src/pyfleet-vehicle-spec:docker_dev
15:37:13.87 [INFO] Completed: Building docker image docker_dev:latest.
15:37:13.87 [ERROR] 1 Exception encountered:

  ProcessExecutionFailure: Process 'Building docker image docker_dev:latest.' failed with exit code 1.
stdout:

stderr:
#1 [internal] load build definition from Dockerfile_dev
#1 sha256:70afa1e12870fb24144364708587cf5d1661f981d416ff91b9933fb09bf718bf
#1 transferring dockerfile: 370B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 sha256:8be3f6d6908bac7ae4d1c83b3c98641278b5369f05b904a5bd61c9aa771021ab
#2 transferring context: 2B done
#2 DONE 0.0s

#3 [internal] load metadata for <http://docker.io/library/python:3.8.1-slim|docker.io/library/python:3.8.1-slim>
#3 sha256:897c30c5b0df12bcc7293f681243e639405b0ad6ce158f8ac7f4d6aa75160f3a
#3 DONE 0.7s

#4 [1/2] FROM <http://docker.io/library/python:3.8.1-slim@sha256:73f3903470a6e55202a6bb989c23b047487eb1728feba655410076da24106838|docker.io/library/python:3.8.1-slim@sha256:73f3903470a6e55202a6bb989c23b047487eb1728feba655410076da24106838>
#4 sha256:28d9be0d3eda75c94bdf3ffcb19aba18126f795be53f25d1fc3ed17716e5e83e
#4 CACHED

#5 [internal] load build context
#5 sha256:d8740fb29f3447aa31b7339dc3205fc961ed6fff4d68fe91e5f24b402262ebf3
#5 transferring context: 2B done
#5 DONE 0.0s

#6 [2/2] COPY requirements.txt /usr/src/app
#6 sha256:962d6b5ae5239ecc9e26d88d359e20065c2a3d56011710983dd0ee0face6bfd1
#6 ERROR: "/requirements.txt" not found: not found
------
 > [2/2] COPY requirements.txt /usr/src/app:
------
failed to compute cache key: "/requirements.txt" not found: not found