https://github.com/pantsbuild/pants/pull/14603 (@happy-kitchen-89482 @fast-nail-55400)

I had an interesting

pants test

failure today that we are having trouble reproducing. Seems almost entirely due to pants/pex based on the error log, but would appreciate guidance on making a bug ticket in the right capacity.

ship it

I'm trying to run a Flask app with debug=True; I saw https://github.com/pantsbuild/pex/issues/1172 and then read through https://www.pantsbuild.org/docs/reference-pex_binary and thought that the solution may be to set execution_mode=venv in the BUILD file. That didn't work, but if I change the Flask app to run with debug=False and then restartable=True in the BUILD file, I get the desired behavior. Is that expected behavior, or should execution_mode=venv also work?

Is it possible to run coverage reports and return an exit code if a threshold is not met? I'd like to have test goal fail based on a percent configured per test target.

Can I get a review on the cp branch? https://github.com/pantsbuild/pants/pull/14606/files

done

@wonderful-yak-59945 You can point Pants at 50937c0f0b2192a1fa85aa63d3f08affe1547328 now, which has the cache fixes in place. Enjoy!

awesome, thank you!

Thanks for the frequent feedback!

One more hopefully simple question. I am trying to resolve constraints and build the

cryptography

library. This requires rust and openssl. It fails to compile because it cannot find headers for openssl.

build/temp.macosx-12.1-arm64-3.9/_openssl.c:575:10: fatal error: 'openssl/opensslv.h' file not found
  #include <openssl/opensslv.h>

I am surprised by this, because I explicitly set some env variables to avoid this.

$ echo $CPPFLAGS $LDFLAGS $PKG_CONFIG_PATH 
-I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib /opt/homebrew/opt/openssl@3/lib/pkgconfig

$ ls /opt/homebrew/opt/openssl@3/include/openssl/opensslv.h 
/opt/homebrew/opt/openssl@3/include/openssl/opensslv.h

What should I change to get cargo to look in the right spot for that file?

Curious if anyone is using Doppler - https://docs.doppler.com/docs - with Pants. It seems like a great fit for a Pants project. I ran into an issue of running a test via Pants that depended on loading env vars from my local .env file, and that wasn't working since the .env file of course isn't in the working directory from which Pants runs a test (there's probably a way to fix that, haven't found it yet). Doppler makes .env files go away though, instead injecting env vars into the Pants process. So running e.g.

doppler run -- ./pants test path/to/test.py

works great (though I still need to configure test/extra_env_vars so that env vars in the Pants env carry over to the env running the tests)

Hey Everyone, I’m trying to add a linter to pants, and I’m struggling to understand from where I should import the object PythonSource referred here https://www.pantsbuild.org/docs/plugins-lint-goal (section two)

Specific use case question. I want to package a PEX binary whos' entry point is a Jupyter server (thinking of the attendant notebooks as resources). I gave it an initial whirl and got it to mostly work, but for whatever reason, when ran from the PEX it does not pick up the configurations in the user's ~/.jupyter, and therefore the resulting server is always private (according to Jupyter's documentation, to expose a non-localhost entry point, you need to specify that in your configuration). When running w/ debug messages, it does state it's checking that location for configurations, which is strange. It also seems that Jupyter does not expose a CLI option to directly override the configuration location (which would be nice so it could just be bundled w/ the binary). I'm sure there are minor details I'm missing and will post more information / logs here later -- but I just wanted to reach out now in case this use case has already been addressed before and the best practices to follow perhaps documented.

Finally, to close this loop, I’ve reported this upstream to Coursier, we’ll see what they have to say about it.

Hi everybody! I’m having a problem generating lockfiles for python, using

./pants generate-lockfiles --resolve=python-default

. I have

ca_certs_path = "/Users/a.../.ca_bundle/certs.pem"

added to pants.toml, but I still get

Updating dependencies
Resolving dependencies...

  SSLError

  HTTPSConnectionPool(host='<http://pypi.org|pypi.org>', port=443): Max retries exceeded with url: /pypi/prefect/json (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1091)')))

  at ~/.cache/pants/named_caches/pex_root/venvs/s/268d4737/venv/lib/python3.7/site-packages/requests/adapters.py:517 in send

I have also set

export REQUESTS_CA_BUNDLE=...

to the same file with the certs, just in case. Is there any other setting I’m missing?

Hi All. I'm trying to think of the best way to implmenet a workflow that builds and deploys a new image, but only if the test passed, but unmemoized. For me that means that it's new code that passed real tests, and that's the only time I want to deploy it (Failed tests obviously won't deploy, and also memoized successes since those already exist in the deployments). What is the best way to go about doing this using Pants? I'm assuming there's a cleaner way than parsing pant's and pytest's stdout? Thanks!

Hi Everyone 🙂 do you know if this error comes from pants “stdout=“Package myproject appears to be a ‘namespace package’ (see PEP 420), which is not currently supported. If this is not deliberate, adding an init.py file should fix the problem.\n” I’m trying to add a new linter, but I’m not sure if the error comes from the linter or from pants itself

hey, anybody got a sample plugin to fill docker_image tags depending on environment variables at hand?

Sanity check - I've got two modules - snowflake-connector-python and snowflake-sqlalchemy - that both map to the name "snowflake". I wasn't able to use python_requirements/module_mapping to express that; I found that only one of those could be mapped to "snowflake", with the last one winning. But I was able to do what's pasted below - that seem like the best approach?

python_requirement(
    name="snowflake",
    requirements=[
        "snowflake-connector-python==2.7.2",
        "snowflake-sqlalchemy==1.3.2"
    ],
    modules=["snowflake"]
)

Hi guys, Does anybody else face an error with golang:

go: updates to go.mod needed, disabled by -mod=readonly; to update it:
        go mod tidy

Thought that it’s because of my local go versions or something, but an example from here works fine on my system, even if delete go.mod and go.sum and create it by myself. What could be the problem. My go.mod looks like:

// private repo
module <http://github.com/{my-org}/{repo}|github.com/{my-org}/{repo}>

go 1.17

require (
	<http://github.com/aws/aws-lambda-go|github.com/aws/aws-lambda-go> v1.28.0
	<http://github.com/fnproject/fdk-go|github.com/fnproject/fdk-go> v0.0.16
	<http://github.com/tencentyun/scf-go-lib|github.com/tencentyun/scf-go-lib> v0.0.0-20211123032342-f972dcd16ff6
)

anyone ever seen this with pants 1 https://gist.github.com/nitay/eac72579b6be32e9054fc42b83d7869a (yes I know it’s old we cannot update to pants 2)

Meet our newest core maintainer, @fresh-cat-90827! https://blog.pantsbuild.org/meet-our-newest-maintainer-alexey-tereshenkov/

is there any reason

pantsbuild.pants

requires PyYAML 6 as a minimum requirement? https://github.com/pantsbuild/pants/blob/main/3rdparty/python/requirements.txt#L21 i believe we use this as an optional dev dependency for typing hints, but this conflicts with a few other dependencies, such as sagemaker: https://github.com/aws/sagemaker-python-sdk/blob/dev/setup.py#L55

FYI a new "good first issue" that would help out the project and hopefully take <30 minutes to do: https://github.com/pantsbuild/pants/issues/14653. tl;dr add a test proving

backend_packages

order is respected, which matters a lot for the

fmt

goal (e.g. run Autoflake before Black/isort)

is it possible to get Pants warnings collected to be able to process later? I’d love to be able to see whether a warning is of particular interest or not (deprecated: something is going to be renamed in version X is not as interesting as _Unmatched glob from_…)

Is there a command to show the dependency path between two targets?

Hello, I'm trying to move an existing project to a monorepo using pants, I am already using pex's and docker builds, this project however uses cython and I can't find any information regarding the plugin you mention in the documentation, could anyone point a link to the plugin or some documentation? thanks!

Hi Everyone, I’m still trying to write a plugin in order to integrate import linter into pants. I’m almost there, but I’m struggling with the path resolution. So I would like to setup the PYTHONPATH in PexProcess using extra_env parameter. How can I get the list of the my pants roots directory so I can set it up in the environment of my linter ?

process_result = await Get(
        FallibleProcessResult,
        PexProcess(
            importlinter_pex,
            argv=[],
            description="Running ImportLinter Playbook...",
            input_digest=merged_digest,
            level=LogLevel.DEBUG,
            extra_env={"PYTHONPATH": ":".join(pythonpath)},
            cache_scope=ProcessCacheScope.PER_RESTART_SUCCESSFUL,
        ),
    )

Re: the multiple resolves feature in Pants 2.10 beta - https://www.pantsbuild.org/v2.10/docs/reference-python#section-enable-resolves - I see the statement about this feature not working if you have VCS requirements. There's also mention of a workaround. Is that workaround specific to the issues with Poetry's lockfile generation, or does it also apply to VCS requirements? And if it doesn't apply to VCS requirements, it seems safe to conclude that if you have VCS requirements (I have 2), then at least for 2.10, you cannot use the multiple resolves feature?