Hi all, is there a way of setting the platform when packaging a

docker_image

target? I’m building an image that I later reference in a

docker_environment

matching that platform value.

Hello 👋! I have starting to scratch pants surface and seems very interesting 😉 . I have a bunch of python repos, every repo goal is to build a docker container with contents depending on files on the repo. I have successfully built docker images using

docker_image

instructions and I can run them using

run container

command. Now, I want to add some integration tests which only pass if container is running to attend requests generated in python_test sections. How I can start a

docker_container

before running

python_tests

? Thx!

I have a venv pex that needs to call an application via subprocess that is also included in the pex. I see the

VIRTUAL_ENV

environment variable is set and also that the

PATH

is inheriting from my terminal. Is there a way I can easily include the

VIRTUAL_ENV

path in my

PATH

variable or do I need to manually export the venv first?

bumping this as I really have no way forward at the moment, starting to feel like Pants may not be in the stars for me - https://pantsbuild.slack.com/archives/C046T6T9U/p1682444973353959 I tried uninstalling and reinstalling pants using homebrew and now pants can't even load a help message, if I just run

pants

I get the same error:

Exception message: Could not initialize store for cache: "Error making env for store at \"/Users/zach/.cache/pants/lmdb_store/cache/8\": No space left on device"

I tried deleting everything in

/Users/zach/.cache/pants

, deleted everything in my docker cache (don't think this would matter), restarted my computer. tried checking out a new copy of the repo I was working on. I also tried creating a new project with a minimal pants.toml setup, same error. short of reformatting my computer I'm really not sure what else to try.

Running

pants test path/to/test/my_test.py

which depends on a directory of data files. These data files are in the same directory, so I suppose these become a

target

. I think I can add these files like so in the BUILD file that lives inside the

test

directory:

python_tests(
    name="tests",
    dependencies=[":mydata"]
)

python_tests(
    name="tests0",

files(
    name="mydata",
    sources=["test-data/*"]
)

So far so good? 🧵 Edit: The issue was that there were two

python_tests

targets. Not sure how this happened. Maybe a

pants tailor ::

coupled with an overzealous read of the docs. I'm new to Pants. 😁

Has anyone come across any good strategies for monorepo versioning when you have related projects (API server, web frontend) and semi-related projects (a background service that runs semi-independently) and general tooling (e.g. CLIs to control admin). I don’t particularly like any of the solutions I’ve used in the past. Generally comes down to each project versioning itself using SemVer or whatever, and then sometimes tagged gift releases representing an important snapshot of the system

I don't know if this is a pants/pex issue, but could not find anything similar. I added pygerrit2 to my requirements.txt and when generating the lockfiles, pants fails with "No distribution metadata found for pygerrit2==2.0.15.". The output before that lists that it runs "creating '/tmp/pants-sandbox-UAgIup/.tmp/tmp7pxml3wz/build/pygerrit2-0.0.0.dist-info'" for some reason. Pip installs the package without issues. I did not find anything weird in the sandbox. Has anyone any suggestions about what to do about this? The breakage starts in 2.16.0.dev7, maybe the upgrade of pex to 2.1.122? But thankfully, 2.17.0.dev4 works fine.

Hey! Having a weird issue when running

./pants fmt

:

AssertionError: Expected ('src/cicd/mutate.py',) to match ('src/cicd/./mutate.py',)

I can do this with some scripting, but maybe there is already a way to list python files that are not used? I vendored in some old code that has a lot of things I don't need and that I don't want to update so that it lints and checks properly.

Anybody out there that has managed to get Colima working alongside

docker_environment

? Getting various errors when trying to do so and assuming I’m missing some config somewhere.

I admit this is somewhat vague, but we run into a lot of problems with M1 pants and python, and thus M1 macs and pants. Many of our M1 mac users are also VSCode users, so I tried to setup a VSCode amd64 "DevContainer" Docker image. The DevContainer image ironically worked on Linux but not Mac :-/ (failure was

pants.pantsd.process_manager.ProcessManager.Timeout: exceeded timeout of 60 seconds while waiting for pantsd to start

). Does anyone have any best practices or examples for running pants from within a vscode DevContainer? (I use neither Macs nor vscode nor arm, so there is a lot of otherwise obvious context I'm probably missing.)

Is it possible to create a command alias to shorten long commands? For example, if I want simplify

./pants test --test-debug --change-since=main --changed-dependees=transitive

into

./pants test-delta-debug

?

Hello, I previously had some plugins built on Pants 2.13.0rc1. After trying to upgrade to 2.14.1, these plugins don’t seem to work anymore when running

./pants --changed-since=origin/master dependees

. The error I’m seeing is the following.

AttributeError: type object 'PythonSourceField' has no attribute 'is_applicable'

Happy to provide code snippets or other additional details

Is there a way to do something like the following: Say

./pants list --filter-target-type=pex_binary ::

gives me

foo:cli

Can I look at all the commits that contain modifications to (transitive) dependencies of

foo:cli

and then get the latest one (on a given branch). I'm interested in this because I want to be able to answer the question is the latest version of

foo:cli

deployed. Maybe an unrelated question. If I wrap everything into a helm chart and use [helm-deployments](https://www.pantsbuild.org/docs/helm-deployments) is the deployment a no-op if none of the dependencies have changed?

So I'm on Pants 2.16.0rc1, testing out the

shell_command

. I have a python project, with python tests, and inside the BUILD file for said tests I've added

python_tests(...)

shell_command(
    command="./just_run_touch_foo.sh",
    tools=["bash", "touch"],
    execution_dependencies=[":scripts"],
    output_directories=["."],
    workdir=".",
    description="this just runs `touch foo"
)

shell_sources(
    name="scripts"
)

What should I expect to happen here? Hoping to see a file

foo

sitting in the directory after the tests run. (Or, at least, inside the sandbox while tests run. So far I have seen neither.) At the current time, my attempt at running the shell command above results in

19:40:00.77 [WARN] No applicable files or targets matched. The `test` goal works with these target types:

  * experimental_test_shell_command
  * python_test
  * shunit2_test

However, you only specified target arguments with these target types:

  * shell_command

I'm pretty sure I don't want to run

experimental_test_shell_command

, as this actually runs a test inside bash script. What I want eventually is to download some canonical dataset that will be used in my unit tests...

Hello all! I am migrating a project to Pants and I have some stateful integration tests that use a real DB. My existing solution is to use https://testcontainers-python.readthedocs.io/en/latest/README.html# , can I use this or something like this with Pants?

Hi, I am trying to setup pants on Mac M1. I am getting below error. Bootstrapping Pants using /Users/vikashanand/anaconda3/envs/andromeda/bin/python3.8 Installing pantsbuild.pants==2.12.0 into a virtual environment at /Users/vikashanand/.cache/pants/setup/bootstrap-Darwin-arm64/2.12.0_py38 ERROR: Could not find a version that satisfies the requirement pantsbuild.pants==2.12.0 (from versions: 0.0.17, 0.0.18, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31, 0.0.32, 0.0.33, 0.0.34, 0.0.35, 0.0.36, 0.0.37, 0.0.38, 0.0.39, 0.0.40, 0.0.41, 0.0.42, 0.0.43, 0.0.44, 0.0.45, 0.0.46, 0.0.47, 0.0.48, 0.0.49, 0.0.50, 0.0.51, 0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60, 0.0.61, 0.0.62, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70, 0.0.71, 0.0.72, 0.0.73, 0.0.74, 0.0.75, 0.0.76, 0.0.77, 0.0.79, 0.0.80, 0.0.81, 0.0.82, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0) ERROR: No matching distribution found for pantsbuild.pants==2.12.0

Hi, is there anything equivalent to the alias target from Pants v1 in Pants v2?

Is there a good convention or action on github actions to set up caching properly there? I'm not super versed in GHA. https://github.com/pantsbuild/actions/blob/main/init-pants/action.yaml looks complicated.

I'm running into a pretty basic issue, maybe I misunderstand the intended usage: When I add

run_against_entire_lockfile = true

to the

pants.toml

, it seems like

pants run <myfile.py>

ends up opening an InteractiveConsole instead of running the python file. If I set to false, then using pants run does run the binary. I can repro this on the https://github.com/pantsbuild/example-python repo, by adding the above and then trying to run

pants run helloworld/main.py

.To note, if I add a pex_binary, I can run that successfully with run_against_entire_lockfile = true.

Hi, sorry if my mistake is so obvious, but I’m having a lot of trouble to skip mypy on test files using defaults. I was looking at this solution https://pantsbuild.slack.com/archives/C046T6T9U/p1671206395059209?thread_ts=1671196289.409119&cid=C046T6T9U but on my test project I’m not able to make it work: https://github.com/anler/pants-playground

If I have a wheel file in my repository (git lfs under the hood).. how can I install that into pants?

Have folks had any luck with

pants-jupyter-plugin

in VS code? If I run a regular notebook the following commands work

%load_ext pants_jupyter_plugin
%pants_repo ../
%pants_load item-rank

but if I try to use the notebook integration in VS code it seems to just hang (specifically `%pants_load item-rank)

I noticed that

pex

2.1.135

venv create

doesn't omit a

__main__.py

in the venv. Is that intentional? The command accepts a

--bin-path

argument but I don't think it does anything unless the

__main__.py

is omitted to the root of the venv

Hey All. I'm sure there is a simple answer to this one... We're looking at options for a new test harness using testcontainers to integrate into our CI pipeline. All is working well if I execute the tests using pytest, however I'm receiving the below error when running the same test in pants:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Any tips?

I'm having hard time making torch work nicely with cuda within pex. To reproduce, consider:

$ docker run --rm -it --gpus all --entrypoint=bash nvidia/cuda:11.7.1-devel-ubuntu22.04

# Inside docker env:
$ apt update && apt install -y python3.10 pip
$ pip install pex
$ pex torch==2.0.0
>>> import torch
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/root/.pex/installed_wheels/7a9319a67294ef02459a19738bbfa8727bb5307b822dadd708bc2ccf6c901aca/torch-2.0.0-cp310-cp310-manylinux1_x86_64.whl/torch/__init__.py", line 229, in <module>
    from torch._C import *  # noqa: F403
ImportError: libcudnn.so.8: cannot open shared object file: No such file or directory

$ pip install torch==2.0.0
$ python3.10
>>> import torch
>>> torch.cuda.is_available()
# etc etc Works fine

Any idea why this might be the case? I need to use this image so that it will work well with EKS' rather outdated GPU driver

Like Pants? Here are some ways you can help more people benefit: • Tell peers why you use Pants and who you think will benefit from Pants too. Spread the word! Whether that be in a casual chat, tweet, blog post, tutorial, presentation, or video. • Contribute to the collaborative spirit of the community by helping a fellow user on Slack or GitHub. • Star the project on GitHub https://github.com/pantsbuild/pants. It's an easy action that helps build exposure and momentum. • Contribute to the docs using the "Suggest Edits" button. • Contribute to the codebase by suggesting an idea, making a feature request, giving feedback on an issue or dev release, opening an issue, or starting a pull request. Looking for a place to start? Check out the `good first issue` tag! • List your organization or open source project on the Who Uses Pants page https://www.pantsbuild.org/page/who-uses-pants • Add a testimonial https://www.pantsbuild.org/docs/testimonials • Publish a case study of how your goals are being served by Pants, either on your blog or ours. This is easily one of the most powerful things you can do!

I've got a Python unit test that needs to call the CLI of a utility that lives in the pex file. Is there a way to make utilities inside the PEX available on the PATH?

Hey Pants Team, curious if we can read version using importlib something like this

VERSION = importlib.metadata.version("my_pkg")

When running with Pants environments we get

E   importlib.metadata.PackageNotFoundError: my_pkg

I found some older thread that suggested to use python_distribution but it seems

version

needs to be hardcoded there but we would prefer to leave version in the

pyproject.toml

. Is there any other ways we can do that with pyproject.toml?

I’m experimenting with

scie-pants

but would like a better way to pin the version of the launcher. Are there plans to accommodate this in

pants.toml

and via the

get-pants

script? (https://github.com/pantsbuild/setup/blob/gh-pages/get-pants.sh)