Hey Pants Team, we've been recently seeing this error when running pants in our CI:

thread panicked while processing panic. aborting.

It seems to happen randomly and not sure how to reproduce. Has anyone seen this before? (using pants version

2.5.0

)

If I need to produce XML from pytest for Jenkins integration I could run it:

pytest --junit-xml junit_test.xml test

How could I pass such option in Pants?

Is there a plan to add backend to support import linter? https://import-linter.readthedocs.io/en/stable/readme.html#

Hello, this is Robert, a pants newbie.

I've trouble running

./pants --version

successfully to get through bootstrapping.

The project that I'm working on uses

pants_version: 1.15.0

with Python 2.7.

The os is Mac OS Big Sur.

The error message I see is raised by

pip

attempting to install

psutil==5.4.8

while trying to compile

psutil/_psutil_osx.c

I was able to fix this separately by patching the C code (was only a minor POSIX related mismatch) and install

psutil==5.4.8

in my virtualenv separately.

Eventually I ended up installing

pip install pantsbuild.pants==1.15.0

successfully into my virtual env.

However, even though when I'm running

./pants --version

the bootstrapping still kicks in and start installing the packages again including the broken

psutil==5.4.8

which, of course, fails the bootstrapping and prevent me to build with

pants

.

Thank you @hundreds-father-404 for the help!!! Greatly appreciated!

In a directory

A

with subdirectories

B

,

C

,

D

(and many others), I want to create a

target()

that encompasses the

:metadata

targets in all subdirectories (so

./B:metadata

,

./C:metadata

,

./D:metadata

and every other subdirectory). Can I use globs to create dependencies? I've tried several glob variations, none of which seem to do what I'm looking for:

**:metadata

./**:metadata

*:metadata

./*:metadata

...

Hi, I'm still playing with

pants_version: 1.15.0

(I know that this is fairly outdated, but can't upgrade right now) and looking into a weird error:

**** Failed to install setuptools-40.4.3 (caused by: NonZeroExit("received exit code 1 during execution of `['/Users/rormandi/.pyenv/shims/python3.9', '-', 'bdist_egg', '--dist-dir=/var/folders/f6/msrc3w_903vb9clkzfzhnrnh0000gq/T/tmpw5xr2p']` while trying to execute `['/Users/rormandi/.pyenv/shims/python3.9', '-', 'bdist_egg', '--dist-dir=/var/folders/f6/msrc3w_903vb9clkzfzhnrnh0000gq/T/tmpw5xr2p']`",)

regarding my Python environment which is

2.7.18

I'm seeing this even after setting

--python-setup-interpreter-constraints='==2.7.*'

and running

./pants clean-all

before the build.

Any advise regarding how could I figure out how and why

pythhon39

is being picked up even after being super explicit about the version of the python repl?

Is there any way to add a dependency on a file in a sibling directory? like

../configs/<current_dir_name>.yaml

? When I try I'm getting errors like:

InvalidSpecPath: Address spec has un-normalized path part '../configs/dummy_pack_1.yaml'

or

InvalidSpecPath: Address spec has un-normalized path part 'st2tests/st2tests/fixtures/packs/dummy_pack_1/../configs/dummy_pack_1.yaml'

Does pants have any native support for handling (prob by ignoring) directories that are git submodules? Or perhaps there's a better approach to solving my problem: One of my test fixtures has to be a git submodule, as the code under test runs

git worktree

. For other directories with similar contents, I can just import something (typically a PATH var to that directory generated with an test infra function). But if I do that across the git submodule boundary, python will fail to import if the git submodule isn't checked out, and pants will complain about any dependencies on that empty directory. (more in the thread)

I have a mono repo (python and scala) that was written some time ago and that developer has left. It used pants.ini, and version 1.24 which is now deprecated. I am trying to update this infrastructure to 2.5 but I can’t find much info on scala support. For instance the build target scala_library is now invalid, most likely because I don’t have it enabled in the pants.toml. Any suggestions? thanks in advance

I could use some ideas on how to deal with this symlink: https://github.com/st2sandbox/st2/blob/pants/st2tests/st2tests/fixtures/packs/core which links to: https://github.com/st2sandbox/st2/tree/pants/contrib/core I'm going to talk about the two distribution paths, to help with understanding why other people added the symlink, but I'm not asking about distribution/archives/etc.

contrib/core

primarily has files+code (in a StackStorm pack) that gets installed with StackStorm itself. But, it is also distributed as part of the

st2tests

module which provides general purpose test fixtures for use in the StackStorm ecosystem. There are a couple of issues with the symlink. The first of which was disambiguating a dependency which was simple enough: https://github.com/st2sandbox/st2/blob/pants/contrib/core/tests/BUILD#L3 The next couple of issues are intertwined: • For all the other fixtures, I used a python import so that pants could infer the dependency from test to fixture. But that get's a little odd with the symlinked code living in two places. •

contrib/core

is a source root (identified by a

[source].marker_filenames

file), but

st2tests/fixtures/packs/core

should not be a source root. Please help me think through what to do about this. I'm not even sure what questions to ask. Any thoughts?

Scratch my head question. On a machine that runs our pexes, I see working jobs using

.pex/install

and

.pex/code

. A new pex I am trying to deploy is failing on not being able to find something on a path that includes

.pex/installed_wheels/

. The only recent change I can think of is we recently updated to

v2.2.3

of pants.

Hi Team, is it possible to package ansible-runner and ansible playbooks using PEX

This is odd. When I run commands with

--no-pantsd

I get colorized output (WARN or ERROR are red). But when running via

pantsd

I don't. Shouldn't it detect that I definitely have a TTY? (using

2.6.0.dev1

)

With my

pants 1.1.15

setup when I try to build one of my python target I'm getting the following error:

...
  File "/Users/rormandi/.cache/pants/setup/bootstrap-Darwin-x86_64/1.15.0/lib/python2.7/site-packages/pex/resolver.py", line 506, in resolve
    return resolver.resolve(resolvables_from_iterable(requirements, builder))
  File "/Users/rormandi/.cache/pants/setup/bootstrap-Darwin-x86_64/1.15.0/lib/python2.7/site-packages/pex/resolver.py", line 288, in resolve
    resolvable_set.merge(resolvable, packages, parent)
  File "/Users/rormandi/.cache/pants/setup/bootstrap-Darwin-x86_64/1.15.0/lib/python2.7/site-packages/pex/resolver.py", line 131, in merge
    self._check()
  File "/Users/rormandi/.cache/pants/setup/bootstrap-Darwin-x86_64/1.15.0/lib/python2.7/site-packages/pex/resolver.py", line 123, in _check
    self._synthesize_parents(name)

Exception message: Could not satisfy all requirements for pyarrow==0.8.0:
    pyarrow==0.8.0

This is python 2.7.16

on MacOSX big sur.

But when I look at the artifact, I can see a whl file for

pyarrow-0.8.0-cp27-cp27m-macosx_10_6_intel.whl