bitter-ability-3219011/13/2023, 5:52 PM
curved-television-656811/13/2023, 5:52 PM
better-van-8297311/14/2023, 3:59 PM
) as discussed here: https://pantsbuild.slack.com/archives/C0D7TNJHL/p1699632752483199. So to make things convenient, we have to use Ruff for formatting AND linting, or not at all. I have a branch up here with an example of the changes: https://github.com/krishnan-chandra/pants/tree/migrate-repo-ruff Let me know if you have any thoughts or questions!
bitter-ability-3219011/14/2023, 6:30 PM
) where the resolve the requirements come from isn't static. Instead you'd set
to say "install from the resolve of the test' source. It's for cases where: • You have
in resolve A. It uses fixtures or whatever, so does
• You also have
in resolve B. Same schtick.
• Their ICs don't overlap So no value of
would work. Not even putting
in its own resolve (because of the imports). Instead
should come from the resolve of the source file.
ancient-vegetable-1055611/14/2023, 6:41 PM
flat-zoo-3195211/14/2023, 8:19 PM
fresh-cat-9082711/19/2023, 8:07 AM
curved-manchester-6600611/20/2023, 2:00 PM
on an internal repo:
• Why does
16:45:09.59 [INFO] Completed: Lint Helm charts - helm succeeded. Partition: cron-ingest-snowflake 16:45:09.59 [INFO] Completed: Lint Helm charts - helm succeeded. Partition: cron-ingest-yes-series 16:45:09.59 [INFO] Completed: Lint Helm charts - helm succeeded. Partition: cron-ingest-rds 16:45:09.59 [INFO] Completed: Lint Helm charts - helm succeeded. Partition: cron-ingest-feast 16:45:11.95 [INFO] Completed: Lint with Hadolint - hadolint succeeded. 16:45:12.00 [INFO] Completed: Lint with Flake8 - flake8 succeeded. Partition: ['CPython==3.10.*'] 16:45:12.00 [INFO] Completed: Format with isort - isort made no changes. 16:45:12.00 [INFO] Completed: Format with Black - black made no changes. 16:45:12.01 [INFO] Completed: Format with Black - black made no changes. 16:45:12.01 [INFO] Completed: Format with Black - black made no changes. 16:45:12.08 [INFO] Completed: Fix with pyupgrade - pyupgrade made no changes.
not have a timestamp/log level? • What is a user supposed to understand from
3 times in a row?
Completed: Format with Black - black made no changes.
broad-processor-9240011/20/2023, 10:10 PM
fresh-cat-9082711/25/2023, 9:49 PM
broad-processor-9240011/27/2023, 7:36 PM
wide-midnight-7859811/28/2023, 3:20 AM
thread 'main' panicked at /Users/sj/.cargo/registry/src/index.crates.io-6f17d22bba15001f/prost-build-0.12.3/src/lib.rs:1521:10: Could not find `protoc` installation and this build crate cannot proceed without this knowledge. If `protoc` is installed and this crate had trouble finding it, you can set the `PROTOC` environment variable with the specific path to your installed `protoc` binary.You could try running `brew install protobuf` or downloading it from <https://github.com/protocolbuffers/protobuf/releases>
ancient-vegetable-1055611/29/2023, 6:23 PM
happy-kitchen-8948211/30/2023, 12:40 AM
late-advantage-7531112/01/2023, 3:36 PM
happy-kitchen-8948212/04/2023, 2:38 AM
fresh-cat-9082712/05/2023, 4:44 PM
$ rm cheeseshop/repository/package.py $ git add cheeseshop/ $ git commit -m "delete file" [main b7f25cd] delete file 1 file changed, 395 deletions(-) delete mode 100644 cheeseshop/repository/package.py $ git log --diff-filter=D --summary | grep delete delete file delete mode 100644 cheeseshop/repository/package.py $ pants --changed-since=origin/main list cheeseshop/repository:repository
late-keyboard-8931412/05/2023, 6:39 PM
targets for multiple platforms, and right now it’s achievable through `environment`s primarily. But given how good Go’s cross-compliation support is, it seems odd to me that there’s (as far as I can tell) no native
way to do that. What I’d propose is something similar to the
field, so you could do something like this for a Go target:
and end up with
go_binary( name="bin" go_os=["linux"] go_arch=["amd64", "arm64"] )
outputs. Thoughts? Is there already a clean way to do this that I’m missing?
happy-kitchen-8948212/05/2023, 8:39 PM
happy-kitchen-8948212/05/2023, 8:39 PM
late-advantage-7531112/06/2023, 2:56 PM
. Daniel caught an error, and it is fixed now, but it will benefit from review from someone else familiar with adhoc_tool. • We're ready to take on the design discussion around the ergonomics part 2 of code_quality_tool which is needed before we announce it. I've summarized some of the proposals around it in https://github.com/pantsbuild/pants/issues/17729#issuecomment-1843036540
wide-midnight-7859812/06/2023, 10:26 PM
late-advantage-7531112/07/2023, 3:21 PM
bitter-ability-3219012/07/2023, 6:56 PM
on one run, another run will be able to see it?