https://pantsbuild.org/ logo
Join Slack
Powered by
In v2.2.0 is this still correct? ```[GLOBAL] pytho...
# plugins
j
In v2.2.0 is this still correct?
Copy code
[GLOBAL]
pythonpath = ["%(buildroot)s/pants-plugins"]
I'm getting 
pants.option.config.Config.ConfigValidationError: Invalid config entries detected. See log for details on which entries to update or remove.
but no details on what config is wrong. I have not found a log file.
h
Yep! What are the invalid entires? It should say a little bit above iirc
j
Copy code
% ./pants --version                                                    cb/chartbeat (CICD-8/pants-v2 :zap:) ip-10-5-0-2
14:10:10.38 [INFO] initializing pantsd...
14:10:11.24 [INFO] pantsd initialized.
14:10:11.29 [ERROR] Invalid config entries detected. See log for details on which entries to update or remove.
(Specify --no-verify-config to disable this check.)
Traceback (most recent call last):
  File "/Users/raul/.cache/pants/setup/bootstrap-Darwin-x86_64/2.2.0rc2_py38/lib/python3.8/site-packages/pants/bin/daemon_pants_runner.py", line 158, in single_daemonized_run
    runner = LocalPantsRunner.create(
  File "/Users/raul/.cache/pants/setup/bootstrap-Darwin-x86_64/2.2.0rc2_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 156, in create
    options.verify_configs(options_bootstrapper.config)
  File "/Users/raul/.cache/pants/setup/bootstrap-Darwin-x86_64/2.2.0rc2_py38/lib/python3.8/site-packages/pants/option/options.py", line 264, in verify_configs
    raise Config.ConfigValidationError(
pants.option.config.Config.ConfigValidationError: Invalid config entries detected. See log for details on which entries to update or remove.
(Specify --no-verify-config to disable this check.)
options_bootstrapper.config
?
But that can't be it because my config does not have 
bootstrapper
in it.
h
Weird that it didn't log it, hmmm. If you can DM your pants.toml, I might be able to eye-ball the issue. Or you can run on 2.1 without ignoring any deprecation warnings and see what is deprecated
I might be able to eye-ball the issue
This isn't sustainable at all. Intent is to unblock you and then we can figure out why the bad entry isn't being printed anymore
j
I can pop back to 2.1.1 and see.
👍 1
pants_distdir_legacy_paths
🍄 ☁️
My 
ignore_pants_warning
settings is probably the problem
is there a way to ignore the 
ignore...
setting on a particular run?
h
My ignore_pants_warning settings is probably the problem
Oh, that could be the culprit! Yes, 
./pants --ignore-pants-warnings='[]' --version
. Note the quotes
j
🙏🏽
h
Lmk if that fixes the config warning not printing, fingers crossed
j
My new CI 0th command: 
./pants --vesion || ./pants --ignore-pants-warnings='[]' --version
\o/
Yeah, it did.
❤️ 1
but I didn't fully test in that I removed the ignore config from the 
pants.toml
file. 😊
bad science
😂 1
I'm going to be a good developer though and leave it to others to test
💯 1
(That didn't quite come out right. I am going to be a good developer by moving forward since I know the problem and got it working. Others can test if 
--ignore...
works. Good developers always test!)
3 Views
Open in Slack
PreviousNext
Powered by