I think I know what happened. Will confirm in a second.

Yup confirmed

When I did my volume mount, that overwrote what was in the container's directory.

Is it possible to explore the first party contents included in a pex binary? Kind of like how if I installed from a wheel, I could go look at

site-packages

or wherever it gets installed to see things.

Yes. And unfortunately

./pants --tag='-integration_test' test ::

doesn't work. And I forget if there is a way to recursively match all test targets with a given name, e.g.

./pants test integration_tests/**::

or something

@high-yak-85899 is this ✅ ?

@rhythmic-battery-45198 is this ✅ ?

Hi, what would be a way to hook-up say a bash script which runs some tests to pants so that these tests are also run when I run

./pants test ::

? We are trying to hook up a tool called

dbt

which basically supports running some tests for transformations defined using sql/ninja.

dbt

has CLI support but not yet mature python support.

@bitter-ability-32190 - I’ve got a very clear answer to my question. Haven’t hosted the wheels yet on my end

I went back to double check if I still needed to pre-build the wheel. The root issue was that the package is only distributed as an sdist, and a pip install option is required to build from source. I came to the conclusion that arbitrary pip options are not supported after searching GitHub issues. Looks like targeted support for the similar —no-binary flag was recently added.

So I think I’m back to needing to host the pre built wheel

Yeah, this was a behavior of how docker mounts volumes and not anything related to Pants.

Hey Pants Team,

update-build-files

goal shows errors to add

name

to

poetry_requirements

but that's not a supported option. Since the

pyproject.toml

lives at the root of the project I believe this error is related:

njgrisafi@Nicks-MacBook-Pro ~/workspace/pants-example (build-file-defaults)$ ./pants lint ::
14:28:42.68 [INFO] Initializing scheduler...
14:28:42.88 [INFO] Scheduler initialized.
14:28:42.93 [ERROR] 1 Exception encountered:

  MappingError: Failed to parse ./BUILD:
Targets in root-level BUILD files must be named explicitly.

example branch: https://github.com/njgrisafi/pants-example/tree/build-file-defaults

Hello, team. I’m trying to execute pants test through GitHub Actions with the attached config (using Pants v2.9) referring to the python example repo. When I make a pull-request, the Action goes properly at first. However, after some commits, the Action fails with the following message on the bootstrap step (it seems that the python execution file is not found). When I also ran the tests or lints on my local environment, those finished properly. How do I fix it?

Run ./pants --version
./pants: line 371: /home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/2.9.0_py39/bin/python: No such file or directory

Hi, why is pants starting and cancelling stuff. I only see this on our CI platform (aws codebuild), not locally though

[Container] 2022/04/08 14:08:25 Running command ./pants test ::
14:08:26.77 [INFO] Starting: Building pytest.pex from pytest_default_lockfile.txt
14:08:26.78 [INFO] Starting: Building requirements.pex
14:08:26.82 [INFO] Canceled: Building pytest.pex from pytest_default_lockfile.txt
14:08:26.82 [INFO] Starting: Building pytest.pex from pytest_default_lockfile.txt
14:08:26.87 [INFO] Canceled: Building pytest.pex from pytest_default_lockfile.txt
14:08:26.87 [INFO] Starting: Building pytest.pex from pytest_default_lockfile.txt
14:08:26.93 [INFO] Canceled: Building pytest.pex from pytest_default_lockfile.txt
14:08:26.93 [INFO] Starting: Building pytest.pex from pytest_default_lockfile.txt

I've adapted the linked plugin to have less weird behavior. Now tests are skipped if manual unless

--run-manual

is specified:

import pytest


def pytest_configure(config):
    config.addinivalue_line("markers", "manual: mark tests which need a person to execute them")


def pytest_addoption(parser):
    group = parser.getgroup("manual", "configuration of manual tests")
    group.addoption(
        "--run-manual",
        action="store_true",
        default=False,
        help="run manual tests",
    )


@pytest.hookimpl(hookwrapper=True, tryfirst=True)
def pytest_runtest_makereport(item, call):
    outcome = yield
    rep = outcome.get_result()
    if call.excinfo and isinstance(call.excinfo.value, pytest.skip.Exception):
        if call.excinfo.value.msg == "manual":
            rep.outcome = "manual"


@pytest.hookimpl(tryfirst=True)
def pytest_report_teststatus(report):
    if report.outcome == "manual":
        return "manual", "M", "MANUAL"


@pytest.hookimpl(tryfirst=True)
def pytest_collection_modifyitems(config, items):
    run_manual = config.getoption("run_manual")

    for item in items:
        if item.get_closest_marker("manual") is not None and not run_manual:
            item.add_marker(pytest.mark.skip("manual"))

Another win for us: migrating python tests and enabled

[python-infer].assets

. • Run test • test fails "No such resource: XYZ" • Add relevant

BUILD.pants

• test succeeds No need to declare the

overrides: {"filename.py": dependencies: ["resourcepath1", "resourcepath2"]}

😈

Does dependency inference work for in-repo extension modules? (E.g. using

python_distribution

)

Do any of the

package

goals support encryption? Like if I wanted to output a symmetrically (or maybe asymmetrically) encrypted pex or tar for deployment somewhere?

Direct support for portable local find-links directories in locks will be available shortly: https://github.com/pantsbuild/pex/pull/1716 - not sure if this goes into Pants 2.11.x, but it will be in 2.12.x. It turns out I needed to have this working to get support for locking local source projects working to round out the recently added support for VCS requirement locking.

Awesome - thanks for the note!

Are the

build_file_aliases

documented anywhere on the docsite?

Hey guys, I am getting a

pex.environment.ResolveError

in

2.11.0rc2

Seems to be related to extra dependencies. Adding details to🧵

Morning all - I am converting our build over to Pants. I have tests running and am trying to get our wsgi app packaged. We have a Pyramid app that is scanning the package to pick up views registered with a decorator. I take it aside from manually listing the views in a BUILD file I would need to create a plugin?

Hi everyone, We have deployed a CICD pipeline using Pants. When the pipeline stops because of an error, we'd want the next run of the pipeline, that was triggered from a commit that contains a fix, to compare the code to the last time the pipeline passed successfully. The way Lerna addresses this in JS is by tagging git commits and compering the current commit to the latest tagged commit. Is there a similar functionality in Pants? Right now it seems that we need to address this ourselves and one would expect from Pants to do that. Thanks!

Hey folks, is there a way to set the terraform version being used to do the

fmt

,

lint

,

check

goals with the experimental terraform backend? Any pointers appreciated!

Hi, a question on MyPy. It seems it takes a long time to build mypy.pex

[2022-04-12T14:27:05.810Z] 10:27:05.59 [INFO] Completed: Building mypy.pex from build-support/mypy_lockfile.txt
[2022-04-12T14:28:27.628Z] 10:28:22.84 [INFO] Long running tasks:
[2022-04-12T14:28:27.628Z]   86.52s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:28:54.377Z] 10:28:52.92 [INFO] Long running tasks:
[2022-04-12T14:28:54.377Z]   116.60s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:29:26.494Z] 10:29:22.95 [INFO] Long running tasks:
[2022-04-12T14:29:26.494Z]   146.63s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:29:53.033Z] 10:29:52.98 [INFO] Long running tasks:
[2022-04-12T14:29:53.033Z]   176.66s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:30:25.092Z] 10:30:23.03 [INFO] Long running tasks:
[2022-04-12T14:30:25.092Z]   206.71s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:30:57.197Z] 10:30:53.08 [INFO] Long running tasks:
[2022-04-12T14:30:57.197Z]   236.76s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:31:23.761Z] 10:31:23.12 [INFO] Long running tasks:
[2022-04-12T14:31:23.761Z]   266.80s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:31:56.020Z] 10:31:53.18 [INFO] Long running tasks:
[2022-04-12T14:31:56.020Z]   296.86s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:32:28.129Z] 10:32:23.22 [INFO] Long running tasks:
[2022-04-12T14:32:28.129Z]   326.90s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:32:54.681Z] 10:32:53.28 [INFO] Long running tasks:
[2022-04-12T14:32:54.681Z]   356.96s	Installing build-support/lockfile.txt for the resolve `python-default`
[2022-04-12T14:33:27.350Z] 10:33:23.34 [INFO] Long running tasks:
[2022-04-12T14:33:27.350Z]   387.02s	Installing build-support/lockfile.txt for the resolve `python-default`

I am wondering if it is related to the cache issue in MyPy mentioned here https://www.pantsbuild.org/docs/python-check-goal#performance-is-often-slower-than-normal?

So there's a few things here: • Building

mypy.pex

finished (probably quickly)

Completed: Building mypy.pex from build-support/mypy_lockfile.txt

• What you're seeing is Pants installing of the dependencies in your resolve. Depending on the size of your resolve, or the size of those deps it can take a while. ◦ This also depends on your settings, which Pants version you're using, and if you're using the new PEX lockfiles • The linked MyPy issue has to do with the performance of running mypy, which you haven't gotten to that step yet 😅

There's tradeoffs to this, but you could disable `[python.resolve_all_constraints`: https://www.pantsbuild.org/v2.11/docs/reference-python#section-resolve-all-constraints Or if you're on Pants 2.11.x, using a PEX lockfile would be extremely performant

@bitter-ability-32190 thanks for info. I am using a lockfile for mypy since I need a different version of MpPy in Pants 2.10, which is the version of Pants I am using.