Andreas Stenius
Andreas Stenius
The confirmation is in the error message: > Unknown flag --execution on docker scope The `docker` scope is from the docker subsystem.
Yea, running off of pants sources constrains your code to Py 3.9, which may result in different resolutions for dependencies. That's my hunch at least.
I can see this being a thing, for sure. However I think it's tricky to get this right and a global flag is likely too coarse, as you'll likely have...
Also hit the issue of cut output. Looks like a bug when you look at it and it is missing output from the beginning of the command. More so than...
I've also had issues with not all the lines at the end being preserved in a block. This is a frequent enough issue for me that I've now benched Warp...
I think it could be worth-while to discover why this restriction was added in the first place, to see if that no longer applies, or if different trade-offs should be...
In the linked issue (https://github.com/pantsbuild/pants/pull/19056) it is mentioned this was only an issue when using token-based auth. See if @thejcannon can fill in more details.
From a CLI perspective: +1 for `path/to/dir` to operate on all targets in dir, not just `path/to/dir:dir`. Especially, as you could make something silly as `src/a/BUILD` ``` python_library() python_tests(name="tests") ```...
+1. I've run across this as well.