#17953 Resolve lockfile paths must be relative Issue created by kaos Pants should present a helpful error message if encountering an absolute path.

I've started to see this issue as well:

./pants --print-stacktrace generate-lockfiles --resolve=black
11:42:49.05 [INFO] Initializing scheduler...
11:42:49.39 [INFO] Scheduler initialized.

11:42:54.99 [INFO] Completed: Generate lockfile for black
11:42:55.00 [INFO] Filesystem changed during run: retrying `GenerateLockfilesGoal` in 500ms...
11:42:55.51 [INFO] Filesystem changed during run: retrying `GenerateLockfilesGoal` in 500ms...
11:42:56.04 [INFO] Filesystem changed during run: retrying `GenerateLockfilesGoal` in 500ms...
11:42:56.55 [INFO] Filesystem changed during run: retrying `GenerateLockfilesGoal` in 500ms...
...

In my

pants.toml

file, I've got the following:

[black]
version="black==22.6.0"
lockfile = "/3rdparty/python/black.lock"

Unsure if I'm doing something wrong on my side. Currently running pants_version =

2.14.0

[SOLVED] Turns out I needed to specify a relative file path e.g

[black]
version="black==22.6.0"
lockfile = "./3rdparty/python/black.lock"

Then it worked 🚀

./pants generate-lockfiles --resolve=black
11:53:53.16 [INFO] Completed: Generate lockfile for black
11:53:53.17 [INFO] Wrote lockfile for the resolve `black` to ./3rdparty/python/black.lock

Originally posted by @JP-Globality in #10705 (comment) pantsbuild/pants