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
If you would like to share a single virtualenv across topologies, you can set "virtualenv_name" in config.json which overrides the default behaviour of using the topology name for virtualenv.
I used it in conjunction with install_virtualenv set to false in order to use an existing virtualenv.
But unfortunately, it doesn't work - I inspected the worker's logs and found that it still used the topology name as the virtualenv name. I inspected the source of Streamparse and found that the virtualenv_name is not included into VIRTUALENV_OPTIONS in streamparse/cli/common.py and therefore it's not returned by resolve_options. The code calling resolve_options in streamparse/cli/submit.py assumes that virtualenv_name might be in the resulting dictionary.
The text was updated successfully, but these errors were encountered:
Documentation says
I used it in conjunction with
install_virtualenv
set tofalse
in order to use an existing virtualenv.But unfortunately, it doesn't work - I inspected the worker's logs and found that it still used the topology name as the virtualenv name. I inspected the source of Streamparse and found that the
virtualenv_name
is not included intoVIRTUALENV_OPTIONS
instreamparse/cli/common.py
and therefore it's not returned byresolve_options
. The code callingresolve_options
instreamparse/cli/submit.py
assumes thatvirtualenv_name
might be in the resulting dictionary.The text was updated successfully, but these errors were encountered: