there is about a 40% chance of my team getting started on supporting JVM languages in the next two months now that we’ve made it past 2.0.0, but there are some other potential language support front runners

as @gorgeous-eve-12553 said though, there are folks who could help someone interested in using the plugin API to get JVM support started.

but also, if it looks like there are a lot of folks interested in JVM support in the community, we might switch up our plans to prioritize it

Personally, I'd rather see first class support for containerization (such as docker) and for k8s.

hi, I am upgrading from pants

2.0.0b1

to

2.0.0

. I have a custom versioning function. while moving between version, I've noticed this output when running

./pants -v

(see attach log file) this is my custom versioning registry.py file

import logging

from pants.base.build_environment import get_buildroot
from pants.backend.python.goals.setup_py import SetupKwargs, SetupKwargsRequest
from pants.engine.addresses import Addresses
from pants.engine.rules import Get, collect_rules, rule, _uncacheable_rule
from pants.engine.target import Target, TransitiveTargets
from pants.backend.python.target_types import PythonProvidesField
from pants.engine.unions import UnionRule

from utilities.versioning import git


class CustomSetupKwargsRequest(SetupKwargsRequest):
    @classmethod
    def is_applicable(cls, _: Target) -> bool:
        return True

# use "@_uncacheable_rule" instead of "@rule" to avoid caching
# Note: from pants team "The API might change a little (probably just a rename), which we'll be happy to help walk through when the time comes that we make it public."
# @rule
@_uncacheable_rule
async def setup_kwargs_plugin(request: CustomSetupKwargsRequest) -> SetupKwargs:
    kwargs = request.explicit_kwargs.copy()
    build_root = get_buildroot()
    target_path = request.target.address.spec_path
    transitive_targets = await Get(TransitiveTargets, Addresses([request.target.address]))
    # in pants v2 files are now the "atomic unit" for Pants, rather than targets
    # <https://www.pantsbuild.org/docs/how-to-upgrade-pants-2-0#files-are-now-the-atomic-unit-rather-than-targets-130-vs-20>
    transitive_dependencies_paths = {tgt.address.spec_path for tgt in transitive_targets.dependencies}
    kwargs["version"] = git.get_version(build_root, target_path, transitive_dependencies_paths)
    logging.info(f'lib name: {kwargs["name"]}, lib version: {kwargs["version"]}')

    return SetupKwargs(kwargs, address=request.target.address)


def rules():
    return (*collect_rules(), UnionRule(SetupKwargsRequest, CustomSetupKwargsRequest))

Hi all, I have a question, I asked something similar in the past, but I still find this a bit strange. Let's say I am running in CI the following command

./pants --changed-diffspec=origin/main --changed-dependees=transitive test

and I have a failing test 1. first time CI runs -> fail 2. I trigger manually another build / push something else unrelated -> pass Is there a way to tell pants to run over "changes + transitive dependees + earlier failures"? Thank you

without running on ::

https://twitter.com/stuhood/status/1322210937391046656 Pants Build retweeted: It's wonderful to see this in production for users! Check out the post. Dependency inference is particularly impor… https://twitter.com/i/web/status/1322210937391046656 Twitter Curious about why "dependency inference" is such a big deal? Read about how it improves the precision of caching in… https://twitter.com/i/web/status/1321960011208142848 Twitter

is there a generally good way to start flask apps in development mode while using

./pants run

? i've got my binary target set up with an entry point

flask.cli:main

, but it seems like it's getting confused by the name of the pex it's run in

I'm not too familiar with Flask. Can you post the error you're getting? I assume

<http://flask.ci|flask.ci>

has a

main()

function that is its entry point?

hey folks! we’re kicking off a prioritization effort today to help guide the project post 2.0! whether you are a past, present, or future Pants user, we need your feedback!: https://groups.google.com/g/pants-devel/c/XMjiqAGITtI/m/6wjMvU_LAQAJ … this is a great opportunity to help get your blocker prioritized, or put a finishing touch on something that is nagging at you!

@astonishing-jelly-60479, @gorgeous-eve-12553: hey folks! we’ve just opened up that feedback gathering process i was mentioning: https://groups.google.com/g/pants-devel/c/XMjiqAGITtI/m/6wjMvU_LAQAJ … would love any ideas you’d like to submit

Question about the

Address(project/src/python/app1/cli/main.py:cli)

object. Are the following statements true? * The part to the left of the colon is always a path to a file relative from the top of the repo. * The part to the right is the name of the target that has the file as a source. * If no target is listed, then nothing owns that file. * When a file has no owner, then

pants

goals using targets will not be able to act on that file.

Say hello to pull request #11111 : https://github.com/pantsbuild/pants/pull/11111

hi! quick suggestion: remove the top nav bar Discussions link (https://www.pantsbuild.org/discuss). it took me a while to realise there is actually somewhere active to ask questions 🙂

@hundreds-father-404

Anything we can help with with trying out Pants?

I have a bunch of questions related to differences from bazel. I have an intermediate level of bazel experience: I've written some very simple rules, and defined the build a medium sized multi-language project. is there some "compared to bazel" doc somewhere?

Hello, everyone! I’m new to Pants and currently testing it out with a work project. I’m having issues getting either the

run

or

test

goals to work. I think the errors are as a result of our directory structure, which looks something like this:

package
 -- src
   -- package
     -- package.py
 -- test
   -- test_package.py
 BUILD

When running

run

, I get an import error:

Error while finding module specification for 'package.package' (ModuleNotFoundError: No module named 'package')

When running

test

, the error is a simple

ModuleNotFoundError

. Has anyone ran into a similar issue?

It seems source roots have been misunderstood on average since inception back in ~2010. Maybe it would make more sense to folks to have per-language options with language-specific terminology that all contributed to the global source root configuration? For example PYTHONPATH for

python

, GOPATH in for

go

and -sourcepath for

javac

.

I am having trouble getting a new CI machine to run a pants test. The tests run successfully when I use the agent on my mac. When I run it on a fully patched Ubuntu 18.04 I get "Code 13: Permission denied":

buildkite-agent@raulcicd:~/builds/raulcicd-chartbeat-net-1/chartbeat/lint-check$ /var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0_py36/bin/pants --level=debug version
Scrubbed PYTHONPATH=/home/ubuntu/superfly from the environment.
10:22:04.81 [DEBUG] acquiring lock: <pants.process.lock.OwnerPrintingInterProcessFileLock object at 0x7faddd0b92e8>
10:22:04.81 [DEBUG] releasing lock: <pants.process.lock.OwnerPrintingInterProcessFileLock object at 0x7faddd0b92e8>
10:22:04.81 [DEBUG] connecting to pantsd on port 44973 (attempt 1/3)
Failed to launch child `/var/lib/buildkite-agent/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0_py36/bin/pants`: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }

I thought it was apparmor at first, but I think I eliminated that as a cause by successfully running scripts in the same directory.

The

pantsd

daemon is running as buildkite-agent:

buildki+ 31558  0.1  2.3 259972 46740 ?        Sl   10:19   0:00 pantsd [/var/lib/buildkite-agent/builds/raulcicd-chartbeat-net-1/chartbeat/lint-check]

aaahh. The PID of the

pantsd

it is trying to connect to is different then the one that is running.

Running with

--no-pantsd

works for

pants version

.

This might be related or a new problem, but it is having trouble finding the correct interpreters:

Exception message: 1 Exception encountered:

  ProcessExecutionFailure: Process 'Find interpreter for constraints: CPython>=3.6' failed with exit code 102.
stdout:

stderr:
Could not find a compatible interpreter.

Examined the following interpreters:
1.) /usr/bin/python2.7 CPython==2.7.17

No interpreter compatible with the requested constraints was found:
  Version matches CPython>=3.6



(Use --print-stacktrace to see more error details.)
buildkite-agent@raulcicd:~/builds/raulcicd-chartbeat-net-1/chartbeat/lint-check$ python3.6
Python 3.6.9 (default, Oct  8 2020, 12:12:24)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

From `pants.toml`:

interpreter_constraints = ["CPython>=2.7.17,<3","CPython>=3.6.9,<4"]
interpreter_search_paths = ["<PYENV>", "<PATH>"]

It’s fine to not use Pantsd in CI, but Stu might want to ask about that issue Hmm, if possible, it’s helpful to run with

-ldebug

to see what Pants is choosing.

Since

raulcicd

sees python3.6 (presumably that's on the

PATH

for

raulcicd

) and

buildkite-agent

doesn't, that provides the 1st clue.

I'm doing tests as the

buildkite-agent

user.

Ah yes.

It's path includes

/usr/bin/

which is where

python

(aliased to

python2

),

python2

,

python3

and

python3.6

are all located.