happy-kitchen-8948212/17/2022, 12:20 AM
args, which means "generate for all resolves" 2) When deciding whether to validate the lockfile header (which we cannot do if we didn't generate the lockfile)
option for this, since it's a list value:
[generate-lockfiles] resolve="-['external1', 'external2']"
enough-analyst-5443412/17/2022, 12:48 AM
over in scie-pants. I'm happy with whatever spelling allows me to continue to generate my own lock files.
[python].resolves_generate_lockfiles = false
happy-kitchen-8948212/17/2022, 2:05 AM
enough-analyst-5443412/17/2022, 2:13 AM
script in that repo!
You can just not runI believe that's untrue. Pants then complains about lack of its invalid header in the lock.
$ git diff diff --git a/pants.toml b/pants.toml index fe9bd78..a2f3f9d 100644 --- a/pants.toml +++ b/pants.toml @@ -43,7 +43,7 @@ enable_resolves = true interpreter_constraints = [">=3.8,<3.10"] # We generate this via cargo run -p package -- --update-lock. -resolves_generate_lockfiles = false +#resolves_generate_lockfiles = false [python.resolves] python-default = "tools/lock.json"
Petards all the way down.
$ dist/scie-pants-linux-x86_64 fmt lint check test package :: 18:20:12.06 [INFO] Completed: Format with isort - isort made no changes. 18:20:12.06 [INFO] Completed: Format with Black - black made no changes. ✓ black made no changes. ✓ isort made no changes. ✓ black succeeded. ✓ isort succeeded. 18:20:12.07 [ERROR] 1 Exception encountered: Engine traceback: in `check` goal in Typecheck using MyPy - mypy InvalidLockfileError: Could not find a Pants metadata block in the lockfile `tools/lock.json` for `python-default`. To resolve this error, you will need to regenerate the lockfile by running `dist/scie-pants-linux-x86_64 generate-lockfiles --resolve=python-default`.
bitter-ability-3219012/17/2022, 2:34 AM
happy-kitchen-8948212/17/2022, 3:20 AM
enough-analyst-5443412/17/2022, 3:52 AM
happy-kitchen-8948212/17/2022, 7:42 AM
bitter-ability-3219012/17/2022, 11:55 AM
hundreds-father-40412/18/2022, 1:43 AM