Hi, I'm upgrading from 1.3 to 2.0 and getting a to...
# general
l
Hi, I'm upgrading from 1.3 to 2.0 and getting a ton of
Unmatched glob
warnings. I tried adding
ignore_pants_warnings = [".*"]
to
pants.toml
but no luck. I also looked at the
files_not_found_behavior
option but it only takes
[warn, error]
and no
ignore
. Are there any ways to completely silence the unmatched glob warnings?
w
hey @late-lawyer-50596! yea, the “ignore” option was deprecated somewhere late in the 1.x series
did i read correctly that you are upgrading from
1.3
(not
1.30.x
)?
it looks like
--files-not-found-behavior=ignore
was removed in
1.30.x
😢 1
l
Yes, I'm upgrading from
1.30.0
w
ah, ok
l
I see I see
w
the ability to ignore warnings should work here. let me look at that.
@late-lawyer-50596: with regard to the actual warnings: in many cases these warnings represent bugs (because a target doesn’t own files that you thought it should). are these cases that just haven’t been fixed yet, or are you noticing legitimate reasons why the globs shouldn’t match?
👍 1
i reproduce a bug in filtering out those warnings (i think because they are generated in native code). let me see if there is a quick fix for that.
👍 2
l
These are cases that haven't been fixed yet. I'm looking to upgrade to 2.0 as soon as possible so fixing them isn't my priority at the moment 😅 There's also ~500 lines of them which will take a while...
👍 1
Thank you for your help!
w
yep, totally.
@late-lawyer-50596: i do have a fix for this. if you’re able to wait ~24 hours, we should be able to get it into the next release candidate for 2.0.x
1
l
That sounds good, thank you!
w
hey @late-lawyer-50596:
2.0.1rc4
and
2.1.1rc2
are out containing this fix