Running into some issues with the `--spec-file` ar...
# general
w
Running into some issues with the
--spec-file
argument specifically the following:
Copy code
Exception: Unmatched glob from file arguments
Not sure I understand why?
one difference being all my testing was conducted with v2 rules and this command failed on a v1 target
w
--spec-file
should be a file containing “specs”
an unmatched glob would mean that one of the specs inside the file was a file glob… ala
tests/**/*.py
or something… and it didn’t match anything
does that sound like the case?
w
hmmm it ddoesnt
let me check
this is the full error message
the spec contains a list of single files, no globs
w
are they newline separated?
Copy code
--spec-file="['<str>', '<str>', ...]" (default: [])
Read additional specs from this file (e.g. target addresses or file names). Each spec should be one per line.
w
uhh yes i think so
w
the error message makes it look like a few might be on one line
w
the file is one per line when i run it locally
however our build system maybe doing something differently
we are saving the command into a bash var before piping it to a file
that might do it
will investigate
thanks!
w
i think it might be… because that error message should render exactly one glob
cool… good luck!
w
appreciate it
h
Hey JP, did you get this working out?
w
@hundreds-father-404 it was EOD for me when we talked about it, so giving it a shot this morning, will keep you posted
💯 1
h
Cool. FYI we just finished documenting what you’re doing https://pants.readme.io/docs/advanced-target-selection, although not sure this says anything new (beyond maybe section on piping Pants)