I am running into a possible bug with the `invalid...
# general
s
I am running into a possible bug with the
invalid_lockfile_behavior
option. Details in thread.
In a particular development branch, I need to ignore invalid lockfile behavior due to the (expected) volatility of one dependency in this branch. But when I set
invalid_lockfile_behavior = "warn"
or
"ignore"
in the pants.toml file, pants still fails while executing a goal for a target that depends on this volatile dependency, complaining of a sha256 mismatch. I tried the option in the toml file, and also the commandline option while running pants. I had to explicitly say
enable_lockfile_resolves = False
to ignore invalid lockfile behavior but that is not something I want to do. Wondering if this is a known issue, or if anyone else has seen this before. Thanks!
Posting this question again to get more eyes 🙂