Which version are you on? We removed watchman from 2.x, have cherry-picked that to 1.30.x to see if CI passes cleanly without it there.

Looking at integration of pants into CI: we're using CircleCI, which uses named caches usually based on the hash of a file (so you'd say have a pip cache based on the hash of

requirements.txt

which is calculated when

requirements.txt

changes, but until requirements.txt changes, that cache doesn't appear to be rebuilt). We can get an approximation to that by manually looking at some files pants uses (can proxy that all requirements.txt files could be hashed together, say) but there are also some internal dependencies that pants sorts through while creating its caches. So my question--is there any way to extract that from pants, to tell when the cache has to be rebuilt? Or is it better to just make a best guess based on all the

requirements.txt

and maybe

BUILD

files hashed together? (sorry if that's unclear; fair amount of flailing here and GARGANTUAN pants caches; still working on the advice in https://www.pantsbuild.org/docs/using-pants-in-ci but ever since our developers started using

torch

any cache just gets punishingly large)

Are there and plugins out there for Sphinx documentation generation with pants or plans to add that capability to pants itself?

set the channel description: Discussion and questions around the Pants build system. If in doubt, post here! We're a friendly bunch.

set the channel topic: If you aren't able to resolve your issue over Slack, please feel free to copy/paste the slack thread (not just the link!) into https://github.com/pantsbuild/pants/issues/new

As you may have noticed, the streamlining of this Slack workspace is complete. See https://docs.google.com/document/d/1f8eu3NWaOjRCKiqTSGt7zVUdASJMCCkxqQdeUvOp6Iw/edit?usp=sharing for background. Enjoy the new, svelte Pants Build Slack!

Let the Pants/Slacks jokes commence, in fact.

Pants project is transitioning to using GitHub Actions instead of TravisCI. The docs currently lead with TravisCI as the canonical example for using Pants with CI. The page could use a few more examples. Adding CircleCI, perhaps? GH Actions is mentioned down the page, but it's not TOC-level topic.

I may meet a framework specific interop bug with pants repo Essentially I try to put a ray.io code into a PEX, and the workers failed to start (cannot find the library it depends)

ModuleNotFoundError: No module named 'ray'
Traceback (most recent call last):
  File "~/.cache/pants/named_caches/pex_root/installed_wheels/a0d5c63d05cf2c837e5e8a0f410c1075f296d621/ray-1.0.1-cp38-cp38-macosx_10_13_x86_64.whl/ray/workers/default_worker.py", line 7, in <module>
    import ray

I found a PEX regression from 4 months ago related to the recursive runtime environment resolve: https://github.com/pantsbuild/pex/issues/1316

<!here> Any issue with the infra for pants init with setting up the version 3.8 for python? CI started failing at the beginning of the pipeline

Quick question about 3rdparty dependencies. If an inline requirement is defined, will this override whatever is defined in the

constraints.txt

file?

@limited-insurance-37393 Hey Tobias -- my name is Liam and I'm a current intern at Toolchain. One of the projects I've started recently has been adding Shiv support per issue 11207. Shiv seems to be a bit sparse on the docs end, and I wanted to check if this was still an issue you felt was important. If so, it would be greatly appreciated if you could provide a minimal example repo with the invocations to package the example app. At the moment, I'm not 100% sure how to include first-party dependencies.

Hi Liam, thanks for taking a look. At the moment it's not a priority for me as I haven't started down the path of using it yet.

https://twitter.com/RealJFairclough/status/1379424319047090178 Pants Build retweeted: Because every timeline needs more baby goats... Twitter

Anyone have any ideas what is causing this weird pex error??

Traceback (most recent call last):
  File "/home/nssvc/talos/.pants.d/run/py/CPython-3.6.8/c0d75e5877b552953184e98f54fba0fb2872d067/.bootstrap/pex/pex.py", line 486, in execute
    self.activate()
  File "/home/nssvc/talos/.pants.d/run/py/CPython-3.6.8/c0d75e5877b552953184e98f54fba0fb2872d067/.bootstrap/pex/pex.py", line 133, in activate
    self._working_set = self._activate()
  File "/home/nssvc/talos/.pants.d/run/py/CPython-3.6.8/c0d75e5877b552953184e98f54fba0fb2872d067/.bootstrap/pex/pex.py", line 118, in _activate
    for dist in env.activate():
  File "/home/nssvc/talos/.pants.d/run/py/CPython-3.6.8/c0d75e5877b552953184e98f54fba0fb2872d067/.bootstrap/pex/environment.py", line 277, in activate
    self._working_set = self._activate()
  File "/home/nssvc/talos/.pants.d/run/py/CPython-3.6.8/c0d75e5877b552953184e98f54fba0fb2872d067/.bootstrap/pex/environment.py", line 453, in _activate
    resolved = self._resolve(working_set, all_reqs)
  File "/home/nssvc/talos/.pants.d/run/py/CPython-3.6.8/c0d75e5877b552953184e98f54fba0fb2872d067/.bootstrap/pex/environment.py", line 331, in _resolve
    distributions_by_key[distribution.as_requirement().key].append(distribution)
AttributeError: 'NoneType' object has no attribute 'as_requirement

This happens inside of a docker container that runs on centos. Pants 1.30.4. Outside of the container the same process runs without issue. The only difference is that its run locally on a mac vs centos.

Hey, I was trying to turn on coverage for my python project and was getting errors. Initially thought it was related to remote execution since I was setting that up, but it fails in CI/CD with remote off as well. Running pants

2.3.0

this worked in

2.2.1

, which was the last version I was using.

[2021-04-06T23:57:47.143Z] ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
[2021-04-06T23:57:47.143Z] __main__.py: error: unrecognized arguments: --cov-report= --cov --cov config --cov dashboards --cov data_lake --cov entity_resolution --cov hooks --cov ml --cov mlop --cov schema --cov task_runner --cov test_fixtures --cov test_util --cov tools --cov util <test file> 
[2021-04-06T23:57:47.143Z]   inifile: None
[2021-04-06T23:57:47.143Z]   rootdir: /tmp/process-execution7UcNHu
[2021-04-06T23:57:47.143Z] 
[2021-04-06T23:57:47.143Z]

I can't repo locally only in CI/CD, so probably an issue there, but I can always repo with remote execution.

Hi guys, pants newbie here. I want to understand what is current status of using pants with macos ARM. I started to work on project which uses 1.30.3, but got into problems very quickly with my new M1 macbook.

This might be a weirdo mac problem, but recently pexs stopped working on my mac, saying no module named pkg_resources

Lawrences-MacBook-Pro-2:aiq lawrencefinn$ python dist/app_admin_tool.pex 
Traceback (most recent call last):
  File "/Users/lawrencefinn/Documents/aiq/dist/app_admin_tool.pex/.bootstrap/pex/pex.py", line 394, in execute
  File "/Users/lawrencefinn/Documents/aiq/dist/app_admin_tool.pex/.bootstrap/pex/pex.py", line 92, in _activate
  File "/Users/lawrencefinn/Documents/aiq/dist/app_admin_tool.pex/.bootstrap/pex/environment.py", line 239, in activate
  File "/Users/lawrencefinn/Documents/aiq/dist/app_admin_tool.pex/.bootstrap/pex/environment.py", line 399, in _activate
  File "/Users/lawrencefinn/Documents/aiq/dist/app_admin_tool.pex/.bootstrap/pex/environment.py", line 143, in _update_module_paths
  File "/usr/local/Cellar/python@2/2.7.17/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/Users/lawrencefinn/.pex/code/7a8afd2b0ab97a76f9819ebfa3858979ce567b61/gen/__init__.py", line 1, in <module>
    __import__('pkg_resources').declare_namespace(__name__)
ImportError: No module named pkg_resources

This used to work, and it works fine on non-mac machines (and maybe other laptops). Im on pants 1.27.0

Hello guys - I have a question about PEX and venv. If I have a PEX and I have a running process - how to drop my process into the venv created with the PEX. Sorry for my ambiguous question here - in the context, I want see a way to allow each worker of ray (process) drop in a venv of a PEX to start an execution.

https://twitter.com/pantsbuild/status/1380407523673395205 Open source dev life! Never know when you’re gonna hear that the free project you've put countless hours into is being used toward a mission that accomplishes marvels. Congrats, @bagder. Very cool. 🚀 Twitter When I received the first NASA email of this kind, I asked the person how they use it. “We are using curl to suppo… https://twitter.com/i/web/status/1380051977401462789 Twitter

I frequently see

Filesystem changed during run: retrying

when running tests, I think mostly while building some pex with requirements that is needed in order to run the goal(s). Feels like there is some paths that get touched during building the pex when requirments are missing and needs to be downloaded, or something like that. No biggie per se, but a bit annoying that it needs to “build” the pex what seems like two times..

$ ./pants test src/python/pants/backend/python/goals/setup_py_test.py 
11:12:48.73 [INFO] Filesystem changed during run: retrying `@rule(pants.backend.python.goals.pytest_runner.run_python_test)` in 500ms...
11:12:48.79 [INFO] Canceled: Building pytest.pex with 6 requirements: ipdb, pygments, pytest-cov>=2.10.1,<2.12, pytest-html, pytest-icdiff, pytest>=6.0.1,<6.3
11:12:48.97 [INFO] Canceled: Resolving 3rdparty/python/constraints.txt
11:13:26.58 [INFO] Completed: Building pytest.pex with 6 requirements: ipdb, pygments, pytest-cov>=2.10.1,<2.12, pytest-html, pytest-icdiff, pytest>=6.0.1,<6.3
11:13:37.15 [INFO] Completed: Resolving 3rdparty/python/constraints.txt
11:13:48.73 [INFO] Completed: Building requirements.pex with 11 requirements: PyYAML<5.5,>=5.4, ansicolors==1.1.8, humbug==0.1.9, packaging==20.9, pex==2.1.38, psutil==5.7.0, pytest<6.3,>=6.0.1, setproctitle==1.2, setuptools<54.0,... (50 characters truncated)
11:13:57.04 [INFO] Completed: Building pytest_runner.pex
11:14:13.37 [WARN] Completed: test - src/python/pants/backend/python/goals/setup_py_test.py:tests failed (exit code 1).

Hmmm…. maybe it is my

emacs

that is the bad guy in this case…

.pants.d/pants.log

11:12:30.96 [INFO] handling request: `test src/python/pants/backend/python/goals/setup_py_test.py`
11:12:34.99 [INFO] Extending leases
11:12:35.06 [INFO] Done extending leases
11:12:48.72 [INFO] notify invalidation: cleared 1 and dirtied 6 nodes for: {".emacs.desktop", ""}
11:12:48.72 [INFO] notify invalidation: cleared 0 and dirtied 0 nodes for: {"", ".emacs.desktop"}
11:12:48.73 [INFO] notify invalidation: cleared 1 and dirtied 6343 nodes for: {"", ".emacs.desktop"}
11:12:48.73 [INFO] notify invalidation: cleared 0 and dirtied 0 nodes for: {".emacs.desktop", ""}
11:13:55.07 [INFO] Extending leases
11:13:55.23 [INFO] Done extending leases
11:14:14.14 [INFO] request completed: `test src/python/pants/backend/python/goals/setup_py_test.py`

Not sure how/if we can exclude the

.emacs.desktop

from the filesystem touched check… ?

Anyone working on golang support for 2.x? If so, where should I hangout and learn/help/ask questions? :)

Is there a way to ignore some modules from when

::

is passed to pants?

I’m getting an ugly

UnicodeEncodeError

when running

./pants dependencies --type=3rdparty ::

Traceback (most recent call last):
  File "./__parse_python_imports.py", line 113, in <module>
    print("\n".join(sorted(string_imports)))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 38-40: ordinal not in range(128)

https://twitter.com/yschimke/status/1380281078070583304 Pants Build retweeted: PSA: If you start work at a big tech company, find a reason to work on some other codebase with a non corporate bui… https://twitter.com/i/web/status/1380281078070583304 Twitter

I'm experiencing an error determining python imports after setting

interpreter_constraints

to

CPython==2.7.*

(this because our project uses a mix of 2.7 and 3.6)

UnicodeDecodeError: 'utf8' codec can't decode byte 0xa0 in position 0: invalid start byte

Pants determines imports fine when I omit

interpreter_constraints

from

pants.toml

. Any ideas why this would occur?

Is there a way to mark one

python_requirements

so that it has higher priority than another? I would like a global way to resolve

>1 target exports this module, so it is ambiguous which to use

, because the global file should always win. There are a couple of packages in the monorepo that, due to how they get deployed, depend on having their own requirements files. So, I added BUILD with

python_requirements

for each of them. But some of those requirements overlap with the global requirements.

https://twitter.com/pyconil/status/1381130062016217093 Pants Build retweeted: PyCon Israel 2021 talk schedule is published! To see the list of the amazing talks go to https://cfp.pycon.org.il/conference2021/schedule/v/0.1/… https://twitter.com/i/web/status/1381130062016217093 Twitter