lively-gpu-2643604/27/2023, 5:19 PM
target? I’m building an image that I later reference in a
matching that platform value.
limited-petabyte-7705404/27/2023, 5:21 PM
instructions and I can run them using
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
ripe-gigabyte-8896404/27/2023, 6:27 PM
environment variable is set and also that the
is inheriting from my terminal. Is there a way I can easily include the
path in my
variable or do I need to manually export the venv first?
swift-river-7352004/27/2023, 7:43 PM
I get the same error:
I tried deleting everything in
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"
, 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.
breezy-mouse-2049304/27/2023, 10:38 PM
which depends on a directory of data files. These data files are in the same directory, so I suppose these become a
pants test path/to/test/my_test.py
. I think I can add these files like so in the BUILD file that lives inside the
So far so good? 🧵 Edit: The issue was that there were two
python_tests( name="tests", dependencies=[":mydata"] ) python_tests( name="tests0", files( name="mydata", sources=["test-data/*"] )
targets. Not sure how this happened. Maybe a
coupled with an overzealous read of the docs. I'm new to Pants. 😁
pants tailor ::
wide-midnight-7859804/28/2023, 1:40 AM
cold-vr-1523204/28/2023, 8:44 AM
famous-xylophone-3653204/28/2023, 9:10 AM
AssertionError: Expected ('src/cicd/mutate.py',) to match ('src/cicd/./mutate.py',)
cold-vr-1523204/28/2023, 11:07 AM
hundreds-carpet-2807204/28/2023, 2:34 PM
? Getting various errors when trying to do so and assuming I’m missing some config somewhere.
curved-manchester-6600604/28/2023, 4:35 PM
). 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.)
pants.pantsd.process_manager.ProcessManager.Timeout: exceeded timeout of 60 seconds while waiting for pantsd to start
rich-london-7486004/28/2023, 4:56 PM
./pants test --test-debug --change-since=main --changed-dependees=transitive
cold-soccer-6322804/28/2023, 7:52 PM
. The error I’m seeing is the following.
./pants --changed-since=origin/master dependees
Happy to provide code snippets or other additional details
AttributeError: type object 'PythonSourceField' has no attribute 'is_applicable'
silly-queen-719704/28/2023, 9:24 PM
./pants list --filter-target-type=pex_binary ::
Can I look at all the commits that contain modifications to (transitive) dependencies of
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
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?
breezy-mouse-2049304/29/2023, 2:46 AM
. I have a python project, with python tests, and inside the BUILD file for said tests I've added
What should I expect to happen here? Hoping to see a file
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" )
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
I'm pretty sure I don't want to run
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
, 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...
gorgeous-eve-1255304/29/2023, 2:50 PM
sparse-intern-1219004/30/2023, 3:30 PM
refined-hydrogen-4796705/01/2023, 9:36 AM
flat-zoo-3195205/01/2023, 7:09 PM
straight-alligator-5464405/01/2023, 7:10 PM
run_against_entire_lockfile = true
, it seems like
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 <myfile.py>
.To note, if I add a pex_binary, I can run that successfully with run_against_entire_lockfile = true.
pants run helloworld/main.py
lively-gpu-2643605/01/2023, 7:36 PM
purple-plastic-5780105/01/2023, 8:46 PM
silly-queen-719705/01/2023, 9:38 PM
in VS code? If I run a regular notebook the following commands work
but if I try to use the notebook integration in VS code it seems to just hang (specifically `%pants_load item-rank)
%load_ext pants_jupyter_plugin %pants_repo ../ %pants_load item-rank
ancient-breakfast-4530305/02/2023, 12:39 AM
doesn't omit a
in the venv. Is that intentional? The command accepts a
argument but I don't think it does anything unless the
is omitted to the root of the venv
rough-camera-1464105/02/2023, 1:14 AM
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
boundless-zebra-7955605/02/2023, 3:44 AM
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
$ 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
busy-vase-3920205/02/2023, 1:19 PM
ripe-gigabyte-8896405/02/2023, 4:38 PM
rapid-bird-7930005/02/2023, 5:34 PM
When running with Pants environments we get
VERSION = importlib.metadata.version("my_pkg")
I found some older thread that suggested to use python_distribution but it seems
E importlib.metadata.PackageNotFoundError: my_pkg
needs to be hardcoded there but we would prefer to leave version in the
. Is there any other ways we can do that with pyproject.toml?
hundreds-carpet-2807205/03/2023, 9:47 AM
but would like a better way to pin the version of the launcher. Are there plans to accommodate this in
and via the