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
When generating the Python licenses using make -c python licenses, these seem to change depending on the environment. In particular, on some envs it's able to fetch the Seldon Core license and in others (e.g. JX cluster) it just returns NONE.
Since the output of the local environment and the CI server may not be the same, this causes false errors on the linting pipeline.
To reproduce
Run make -C python install_dev licenses
Depending on the environment, the ./python/licenses/license.txt file will list SC's license as NONE or as Apache.
Expected behaviour
The make -c python licenses command should be able to fetch SC's correct license (i.e. Apache) and not change between environments.
The text was updated successfully, but these errors were encountered:
adriangonz
changed the title
Python licenses seem to change depending on the environment
Python licenses change depending on the environment
Jul 14, 2020
Describe the bug
When generating the Python licenses using
make -c python licenses
, these seem to change depending on the environment. In particular, on some envs it's able to fetch the Seldon Core license and in others (e.g. JX cluster) it just returnsNONE
.Since the output of the local environment and the CI server may not be the same, this causes false errors on the linting pipeline.
To reproduce
make -C python install_dev licenses
./python/licenses/license.txt
file will list SC's license asNONE
or asApache
.Expected behaviour
The
make -c python licenses
command should be able to fetch SC's correct license (i.e.Apache
) and not change between environments.The text was updated successfully, but these errors were encountered: