I am trying to update to

2.12.0.dev2

for the new

rule_helper

function and getting this:

ERROR: No matching distribution found for pantsbuild.pants==2.12.0.dev2

looks like the package is up there though. Any idea what is going on?

I have question about thrift BUILD file. This is my BUILD file:

thrift_sources(
    name='gen',
    sources=['*.thrift'],
)

When I run ./pants run …, I got this:

Could not find include file xxx.thrift

It looks like it couldn’t find each other in the same folder. How do I fix this?

Hi , how do I deal with

ERROR: Could not find a version that satisfies the requirement myproject.common==1.0
ERROR: No matching distribution found for myproject.common==1.0

This is a package that only used in my org. How do I add the path of the file? Back in the days there was a

repository

field to specify the path.

python_requirement(
    name='myproject.common', 
    dependencies=[':salt', ':pymysql'],
    requirements=[
        'myproject.common==1.0',
    ],)

I brought this up previously, but I'm a different person now. How should I address running binaries which produce/edit files which should be reflected in my workspace?

The common pants way to do things is to put

BUILD

files in all directories. Is there any way to make a

python_distribution

that does something like

src/my_project::

in the

dependencies

section? Am I forced to make a

pyproject.toml

to do that specifying?

A new "Good First Issue": Required fields should sort first on the docsite 🙋 *https://github.com/pantsbuild/pants/issues/15147

Hi, I just upgraded to 2.10 and fix all the BUILD file errors. Now I am trying to build pex. It seems to take forever… Any suggestion?

$ ./pants run bin:xxx
⠠ 867.12s Building xxx.pex with 77 requirements: ...

Blogger here: Per https://www.pantsbuild.org/page/language-support, Pants2 has support for Go, Java, Python, and Scala (I’m counting the 3GLs only, but i spy Thrift, Protobuf too). JavaScript/TypeScript is a wished for direction. Have I got the number right?

Hi, I was running

./pants test …

and got this error:

ProcessExecutionFailure: Process 'Building requirements.pex with 23 requirements: ...

How do I fix this? I will put the full log in thread.

Does anyone know where one can view the source(/contribute to) the Github Actions

pantsbuild/actions/expose-pythons

? (Context, I'm investigating picking up the PR for adding a Windows CI and support for Windows into Pex, but I'm stuck on an error that is coming out of this action)

Hi! I'm getting this error after adding

pants.backend.docker

to the list of backend packages:

ModuleNotFoundError: No module named 'pants.backend.docker.register'
09:50:00.53 [ERROR] Failed to load the pants.backend.docker.register backend: ModuleNotFoundError("No module named 'pants.backend.docker.register'")

has anybody faced this issue?

Facing a new issue: when trying to build a pex binary pants is not respecting the interpreter constraints and building it with a different version of python, resulting in this error when I try to run the docker container:

ResolveError(
pex.environment.ResolveError: Failed to resolve requirements from PEX environment @ /root/.pex/unzipped_pexes/1bc1b3d05270a6cb192aecf5a51715e951da993c.
Needed cp39-cp39-manylinux_2_31_x86_64 compatible dependencies for:
 1: MarkupSafe>=2.0
    Required by:
      FingerprintedDistribution(distribution=Jinja2 3.1.1 (/root/.pex/installed_wheels/0893af5400986fb3b6c0f06db963e45dd7e2e9be91f476133910371878af80e8/Jinja2-3.1.1-py3-none-any.whl), fingerprint='0893af5400986fb3b6c0f06db963e45dd7e2e9be91f476133910371878af80e8')
    But this pex had no 'MarkupSafe' distributions.

in `pants.toml`:

[python]
interpreter_constraints = ["CPython==3.9.10"]

debug logs when running `./pants package src/app/Dockerfile --level=debug`:

10:39:20.62 [DEBUG] Completed: Find Python interpreter for constraints - Selected /Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/bin/python3.8 to run PEXes with.

Hi all, sorry for some questions on using pants - I just started trying to use it for a monorepo with existing projects. While I've hit a few issues, I'm currently trying to understand this "least astonishment" issue for pants with python. I suspected that pants would use either my currently activated virtual environment (default to

python

in the

PATH

) or otherwise use my system python from MacOS. however, it seems to behave in a completely unexpected way. In the output (see thread), you can see that I'm running in a

3.10

venv, pants uses a seemingly random

3.9

binary from my pyenv shims, and then when the goal is run, it uses a

3.7

binary (maybe the original system binary?).

FYI new "good first issue": teaching dependency inference for thrift to handle relative imports. Fairly small change that will show you how dependency inference works under the hood. https://github.com/pantsbuild/pants/issues/15152

I ran into an issue with BinaryNotFoundError when running in our self-hosted runner (we haven't successfully done this before)

Hi Pants team, can pants handle the libs imported programmatically (e,g, via import_module)? From my observation, pants does not seems automatically handle them? I can add those libs manually in BUILD files, but there are lots of them in my use case. I could also ‘consolidate’ those BUILD files by combining them and moving it to a parent folders. But, in that case, the dependencies feature will be ‘lost’ in some way as every thing in the parent folder will depend on all those libs manually added. Any suggestion to handle it better?

Hello, I'm running into some issues with pants

2.10.1rc0

(and

2.10.0

) where a

python_distribution

will generate a

.tar.gz

which gets enumerated by

isolate_local_dist_wheels

and subsequently fails when

unzip -Z1

returns a non 0 exit code because it has no idea what to do with a

.tar.gz

I am trying to turn on pants-based linting for more of our python files, but am running into an error that doesn't make sense to me, which works when using pylint directly–

src/django_apps/files/models.py:21:0: E0401: Unable to import 'util.url' (import-error)

Though pants shows them as a dependency:

$ p dependencies src/django_apps/files/models.py
...
src/util/url.py

What am I missing here?

I’m seeing some error messages in CI that I’m not sure how to parse:

20:40:20.36 [WARN] Failed to read from remote cache (1 occurrences so far): Error saving remote output directory: Tree with digest Digest { hash: Fingerprint<9b9b5334c93106332e06ff5ea71502451964b70a1b2a9c0d52e021cd26203f57>, size_bytes: 260 } was not in remote

specifically I’m confused that it says both

failed to read

and

error saving

- one I might expect on a cache-miss, but the other would indicate some misconfiguration with our remote caching setup (I think?)

~we’re only seeing a 27% hit rate from our remote cache which makes me think something is busted EDIT: the job I was looking at modified

pants.toml

so I’m guessing that was the cause of the above. we’ve been doing a lot of modification to that file so maybe that’s why we miss the cache so often. leaving the above as a request for a more clear error message 🙂

New feature! Thanks to @sparse-lifeguard-95737,

export

in 2.12 will now export a venv for each tool Pants uses like

black

and

isort

. So, you can point your IDE to use those binaries. Thank you!

is there a way of controlling amount of memory used by nailgun in JVM processes? or limiting the number of the nailgun servers spawned in some way or another? We are experiencing some crashes when trying to build our codebase (when trying to build a large number of JVM targets). In Linux machines the error is:

Exception: Error communicating with server: Client exited before the server's result could be returned.

Which makes me think that the nailgun server process was killed/crashed. In MacOS the result is more dramatic, after a while you start getting warnings from the OS saying that you are out of memory leading to the whole computer crashing. The only way we have found now to control this is by using

[GLOBAL].process_execution_local_parallelism

, which is a blunt hammer as it affects all processes.

Having some trouble getting

pants_ignore.add

to not ignore a `.gitignore`d dir.

# .gitignore
/deps/libs/*/versions/

# pants.toml
pants_ignore.add = [
    "!/deps/libs/thing/versions/active",
]

# deps/libs/thing/BUILD.pants
files(
    name="srcs",
    sources=["versions/active/src/**"],
)

Results in:

Unmatched glob from deps/libs/thing:srcs's `sources` field: "deps/libs/thing/versions/active/src/**"

Hello. I have some test data in a specific folder structure. I am trying to access that data when running a test case. I have used the files() target type, but it doesnt pickup the subfolders structure

Hi, is there some standard way of handling python sub-packages which aren't necessarily imported inside but the package under which these sub-packages live. These sub-packages are just a way to modularize the code base. e.g.

package
  BUILD
  __init__.py
  -- sub-pkg1
  -- sub-pkg2

then later we do say for testing

from package.sub-pkg1 import func1

pants will complain that this

package.sub-pkg1

isn't a package since it can't infer the dependency unless I explicitly add in BUILD

sub-pkg1

as dependency for

package

. Basically is there a way around providing this explicit dependency in such case.

Found some weird behaviour - pants can't seem to find some sub package called

lib

, but I can list the directory. Please see the 🧵

Does anyone know how to access environment variables in the pants.toml for a index url? I need to access creds for a private pypi repo

[python-repos]
indexes.add = []

Hi, when I use pants to run unit test, I used to do like

./pants test xxx:all_test

And there would be a

BUILD

file under

xxx

like this:

target(
    name='all_test',
    dependencies=[
        ':aaa',
        ':bbb',
    ],
)

and then it will look into

aaa

and

bbb

recursively to find

python_tests

but in this newer version (2.10) of pants when I do the same thing, I will get this warning:

22:51:00.65 [WARN] No applicable files or targets matched. The `test` goal works with these target types:

  * junit_test
  * python_test
  * scala_junit_test
  * scalatest_test

However, you only specified targets with these target types:

  * target

and it doesn’t run any test. What should I do to make

BUILD

files behave like they did in the past?

Hi @hundreds-father-404 I am wondering if you have the relevant docs for pants 2.11. The problem I am facing now is that, in our CI, the unittests are used to complete very fast assuming the conda env is there. But with Pants, given it needs to resolve those dependencies, running unittest become very slow. I am wondering if the PEX lockfile can solve/help this issue? or do you have any other suggestion?

Hi, i'm using pants 2.8 and have issues with dependency resolution. i have a package in a custom registry (which unfortunately has a name conflict with a package in pypi, but due to historical reasons and i cannot change it) and use poetry with a constraints file for deps handling. my constraint file has the extra index specified and when i use just an ordinary venv and install everything with pip everything works out fine. however, when using pants, my dependency is simply not recognized, e.g. "Completed: Extracting 5 requirements to build requirements.pex from repository.pex: inflection==0.5.1, ... pantsbuild.pants==2.8.0, pydantic==1.9.0, ... " and here my dependency is missing and i get quite a lot of import-errors (e.g. from the linter and so on). Any ideas how i can debug this properly or what could be a potential issue? cheers,