Presumably related to #9714, cc @witty-crayon-22786

@happy-kitchen-89482: need to rebase

that’s a bootstrap misalignment

I did, so I thought

… might have hit John’s change instead then, heh

Just rebased again

should be good now

Has cache-read/write-from/to moved into a backend or something (for the binary and test goals, python)? Noticed v2 is no longer using the remote cache we had set up. And I no longer see the options in --help.

$ curl -L <https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar>
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>AKIAIWNJYAX4CSVEH53A</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256
20200507T222851Z
20200507/us-east-1/s3/aws4_request
0c5ecf44cc002fac2ead335e2a54a9e20e9de1cf76da52a1a17ce8e0ee2c00de</StringToSign><SignatureProvided>70228659c7e0c4670b5040b5815348d07da5746b47a2f8edc05e118833127b23</SignatureProvided><StringToSignBytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 32 30 30 35 30 37 54 32 32 32 38 35 31 5a 0a 32 30 32 30 30 35 30 37 2f 75 73 2d 65 61 73 74 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 30 63 35 65 63 66 34 34 63 63 30 30 32 66 61 63 32 65 61 64 33 33 35 65 32 61 35 34 61 39 65 32 30 65 39 64 65 31 63 66 37 36 64 61 35 32 61 31 61 31 37 63 65 38 65 30 65 65 32 63 30 30 64 65</StringToSignBytes><CanonicalRequest>GET
/37548601/0e0f2b80-f589-11e8-8104-6e1704d2d3c2
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200507%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200507T222851Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&actor_id=0&repo_id=37548601&response-content-disposition=attachment%3B%20filename%3Dcoursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar&response-content-type=application%2Foctet-stream
host:<http://github-production-release-asset-2e65be.s3.amazonaws.com|github-production-release-asset-2e65be.s3.amazonaws.com>

host
UNSIGNED-PAYLOAD</CanonicalRequest><CanonicalRequestBytes>47 45 54 0a 2f 33 37 35 34 38 36 30 31 2f 30 65 30 66 32 62 38 30 2d 66 35 38 39 2d 31 31 65 38 2d 38 31 30 34 2d 36 65 31 37 30 34 64 32 64 33 63 32 0a 58 2d 41 6d 7a 2d 41 6c 67 6f 72 69 74 68 6d 3d 41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 26 58 2d 41 6d 7a 2d 43 72 65 64 65 6e 74 69 61 6c 3d 41 4b 49 41 49 57 4e 4a 59 41 58 34 43 53 56 45 48 35 33 41 25 32 46 32 30 32 30 30 35 30 37 25 32 46 75 73 2d 65 61 73 74 2d 31 25 32 46 73 33 25 32 46 61 77 73 34 5f 72 65 71 75 65 73 74 26 58 2d 41 6d 7a 2d 44 61 74 65 3d 32 30 32 30 30 35 30 37 54 32 32 32 38 35 31 5a 26 58 2d 41 6d 7a 2d 45 78 70 69 72 65 73 3d 33 30 30 26 58 2d 41 6d 7a 2d 53 69 67 6e 65 64 48 65 61 64 65 72 73 3d 68 6f 73 74 26 61 63 74 6f 72 5f 69 64 3d 30 26 72 65 70 6f 5f 69 64 3d 33 37 35 34 38 36 30 31 26 72 65 73 70 6f 6e 73 65 2d 63 6f 6e 74 65 6e 74 2d 64 69 73 70 6f 73 69 74 69 6f 6e 3d 61 74 74 61 63 68 6d 65 6e 74 25 33 42 25 32 30 66 69 6c 65 6e 61 6d 65 25 33 44 63 6f 75 72 73 69 65 72 2d 63 6c 69 2d 31 2e 31 2e 30 2e 63 66 33 36 35 65 61 32 37 61 37 31 30 64 35 66 30 39 64 62 31 66 30 61 36 66 65 65 65 31 32 39 61 61 31 66 63 34 31 37 2e 6a 61 72 26 72 65 73 70 6f 6e 73 65 2d 63 6f 6e 74 65 6e 74 2d 74 79 70 65 3d 61 70 70 6c 69 63 61 74 69 6f 6e 25 32 46 6f 63 74 65 74 2d 73 74 72 65 61 6d 0a 68 6f 73 74 3a 67 69 74 68 75 62 2d 70 72 6f 64 75 63 74 69 6f 6e 2d 72 65 6c 65 61 73 65 2d 61 73 73 65 74 2d 32 65 36 35 62 65 2e 73 33 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 0a 68 6f 73 74 0a 55 4e 53 49 47 4e 45 44 2d 50 41 59 4c 4f 41 44</CanonicalRequestBytes><RequestId>1B5A496843649545</RequestId><HostId>MWnvcuSBMVFk+RUmFgBsbbxXnh8YB0P+2gZIxCOKexkAZ0812r8kqNgCI8r3Xz4ZNXS/Ha0veLc=</HostId></Error>

Any ideas?

Pre-commit hooks are failing for me with:

Exception message: 1 Exception encountered:
Computing Select(ExternalToolRequest(url_to_fetch=UrlToFetch(url='<https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar>', digest=Digest(fingerprint='24945c529eaa32a16a70256ac357108edc1b51a4dd45b656a1808c0cbf00617e', serialized_bytes_length=27573328)), exe='coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar'), DownloadedExternalTool)
  Computing Task(pants.core.util_rules.external_tool:232:download_external_tool(), ExternalToolRequest(url_to_fetch=UrlToFetch(url='<https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar>', digest=Digest(fingerprint='24945c529eaa32a16a70256ac357108edc1b51a4dd45b656a1808c0cbf00617e', serialized_bytes_length=27573328)), exe='coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar'), DownloadedExternalTool, true)
    Computing DownloadedFile(UrlToFetch(url='<https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar>', digest=Digest(fingerprint='24945c529eaa32a16a70256ac357108edc1b51a4dd45b656a1808c0cbf00617e', serialized_bytes_length=27573328)))
      Throw(Client error (403) downloading file coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar from <https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar>)
        Traceback (no traceback):
          <pants native internals>
        Exception: Client error (403) downloading file coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar from <https://github.com/coursier/coursier/releases/download/pants_release_1.5.x/coursier-cli-1.1.0.cf365ea27a710d5f09db1f0a6feee129aa1fc417.jar>

Curling fails for me too:

What does it mean when pants says

foo is source but does not belong to a package.

how do I make sure

foo

is part of a package? It should be covered by

rglobs(*.py)

in the BUILD file.

added an integration to this channel: twitter

Hi @witty-crayon-22786, would you kindly take a look at https://github.com/pantsbuild/pants/pull/9707? If it looks good, would also appreciate a publish.

Hi, we were using scala 2.12 as our default scala library, but some of the user need to work with scala 2.11 is there a way we can define multiple scala version in

pants.ini

as

jvm-platform

? or the only way is to set a

--scala-version

options from command line?

https://twitter.com/pantsbuild/status/1258797562540093440 Pants Build retweeted: Long-time committer @benjy will be giving a talk for the SF Python Meetup (this Wednesday!) about how Pants' v2 API… https://twitter.com/i/web/status/1258797562540093440 Twitter

Running into some issues with the

--spec-file

argument specifically the following:

Exception: Unmatched glob from file arguments

Not sure I understand why?

If anyone's interested, details of my Zoom talk later tonight at the SF Python meetup: https://www.meetup.com/sfpython/events/xkwxvqybchbrb/

Will post video when I have it

While waiting for Benjy's talk, I was playing around with upgrading our 1.18.0 repo to 1.28.0rc1. I am running into a problem following the docs around

--source-source-roots

option. In our old

pants.ini

file the section is defined as a dictionary like so:

[source]
source_roots: {
    "3rdparty/go": (u"go_remote",),
    "contrib/go/examples/3rdparty/go": (u"go_remote",),
    "app1": (u"python",),
    "app2": (u"python",),
    }

When I translate this to TOML:

[source]
source_roots = """{
    "3rdparty/go": "(u'go_remote',)",
    "contrib/go/examples/3rdparty/go": "(u'go_remote',)",
    "app1": "(u'python',)",
    "app2": "(u'python',)",
    }"""

I get the following error

DeprecationWarning: DEPRECATED: option 'source_roots' in scope 'source' will be removed in version 1.30.0.dev0.
  Use --roots instead.

If I change

source_roots

to

roots

I get this error

Invalid option 'roots' under [source] in /Users/raul/dev/cb/chartbeat/pants.toml

. When I go to https://pants.readme.io/docs/source-roots it only talks about

root_patterns

. So I am confused about what to change the

source_roots

to. And I should note, that works because I can see my settings when I run

./pants --no-verify-config help-advanced source

Great talk, @happy-kitchen-89482!!! I can't wait to post it on my work's #pants_indoctrination channel.

Hey, I'm just curious as to a higher level explanations of differences between Bazel and Pants. From a general overview, I see that they both have the same aim and the BUILD files look remarkably similar. • One issue I constantly come across is how to control the toolchain in Bazel. Many developers get around this by just hosting everything in a docker sandbox and allowing the use of host tools or force developers to execute remotely in carefully controlled containers. Others create verbose "toolchain" config files, such as this for C++: https://github.com/codificasolutions/bazel-cross-compile-example/blob/master/toolchain.bzl and try to maintain a custom set of rules. Others use a macro known as

rbe_autconfig

which tries to guess what the toolchain would be in your docker container. I'm unsure if any of these solutions are optimal at the moment so I wanted to know if you did things differently? • Why a deamon? I notice Bazel does the same (or at least similar) and you mention in your documentation it is to keep "the action graph warm" - does that mean you're just doing this to keep the action graph in memory? Do you watch for any files that change and update the action graph in the background? • Does anyone know how the generation of an action graph differs? I assume at a basic level you both try to achieve the same thing. You create a DAG and look what needs rebuilding in the tree when an Action changes. After that, is it just what a Bazel rule and Pants rule actually define as an Action? • How does one create a build rule for Pants? A very brief look at your documentation doesn't elude to any easy way to create a plugin. Though that could be just me not being thorough enough.

Small bit of feedback on file arguments: we frequently keep README files next to the code in our repos for documentation / runbooking etc. Recently ran into a build issue where changing a readme triggered a . failure:

Please check that there is a BUILD file in `src/media_processing/xcoder_audio_levels` with a target whose `sources` field includes `src/media_processing/xcoder_audio_levels/README.md`. See <https://www.pantsbuild.org/build_files.html>.

Naturally, these files do not belong to a target since they are not runtime artifacts. If there is an option to safely ignore 'orphaned' files, consider including that in the error message. If there isn't would like to kindly request one as building a good exclustion list can become quite cumbersome

שלום @polite-garden-50641

hi @witty-crayon-22786

Any ideas how to implement https://github.com/pantsbuild/pants/pull/9804 properly? (as what i tried didn't work)

(or @hundreds-father-404)

I suppose I should have filed an issue for it...