You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[doc] Print a better error message when the hub repo aliases do not match config settings #2466
The general design would be to create our own no_match_rule which could be instantiated as follows:
defcompatible_settings(settings):
"""Return a list of strings"""ret= []
forsettinginsettings:
ret+=select({setting: [setting], "//conditions:default": []})
returnretno_match(
name="no_match",
compatible_settings=compatible_settings(ALL_SETTINGS),
# The flags that we use for selecting the wheelspython_version="@rules_python//python/config_settings:python_version",
...
)
This would trigger the _impl rule implementation above and it would fail building the target.
Definition of done:
We can see compatible config settings with the current configuration.
We can see the flag values of the current configuration.
If we do bazel build //_config/..., the build should not fail. Add a build_test in the //tests/pypi/integration.
We have an analysis test that checks the failure and (bonus points) checks that the error message is templated with the correct compatible settings. Add an analysis test in //tests/pypi/pkg_aliases.
Activity
doc(pypi): A better error message when the wheel select hits no_match
refactor(pypi): A better error message when the wheel select hits no_…