Stu Hood
Stu Hood
The `pants` script in the `pantsbuild/pants` repo builds a venv directly from an unpinned `requirements.txt` file: this means that it can bootstrap non-deterministically. As an example: `strawberry` transitively depends on...
As described in https://github.com/pantsbuild/pants/issues/18889, it seems like our initial use of the crate ended up hardcoding a single `DOCKER_HOST` handling mechanism, since there isn't a single `Docker::connect_with_*` method that would...
As discussed in #20572, this change adds a built-in goal `migrate-call-by-name` which emits all `Get` calls which should be migrated to call-by-name syntax. A followup change should use the resulting...
(as motivated in #18905) Implementation: 1. `rule_graph` crate changes: * [x] adjust the definition of `Get` (`DependencyKey`) for rule-graph solving to accept a fixed name/identifier for the rule to use,...
To complete #19730 by migrating Pants itself and any in-repo plugins to call-by-name syntax, we should create a built-in goal which would: 1. Take as argument a list of modules...
Currently the scala `repl`: 1. defaults to using `python` unless `repl --shell=scala` is specified (even if the `python` backend isn't enabled) 2. fails if a target has `resources` dependencies (likely...
Pants uses lots of PEXes "internally", which are never exported for users to consume. Since these are implementation details, we have free-rein to choose an internal-default [PEX compression level](https://github.com/pantsbuild/pex/pull/1705)... and...
With `coursier` `2.0.16` and `2.1.7`, the following command: ```bash cs fetch --json-output-file example.json org.apache.hive:hive-exec:1.1.0 --exclude org.apache.calcite:calcite-avatica --exclude org.apache.calcite:calcite-core --exclude jdk.tools:jdk.tools ``` ...produces a JSON report containing undefined _transitive_ dependencies. In...
As discussed in the previous [Pants Team Meetup](https://docs.google.com/document/d/1LhGXW2kwaV4u1uqz_GvYe9fbeQilJLbCJ49kGxBOKe4/edit?pli=1), we think that the stable release process requires some dedicated attention, so we'd like to choose a dedicated stable release manager per...
Currently, the `docker::CommandRunner` hardcodes use of `Docker::connect_with_local_defaults`, which under the hood assumes unix domain sockets are in use (i.e. that [DOCKER_HOST](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-socket-option) is a `unix://` connection string). It seems clear based...