Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

volttron start fails in develop #3154

Closed
schandrika opened this issue Feb 21, 2024 · 0 comments
Closed

volttron start fails in develop #3154

schandrika opened this issue Feb 21, 2024 · 0 comments
Assignees

Comments

@schandrika
Copy link
Contributor

Describe the bug
Starting volttron with develop branch code fails with
"ModuleNotFound: No module named "requirements"

This does not happen in main

Cause - current directory -i.e. volttron root directory is not sys.path. This gets added automatically to path when volttron is built using code in main branch. However current directory is not getting added to sys.path when volttron is built and run from develop. Both branches use same version of python, setuptools, and all other libraries

Solution/workaround
requirements.py is at the root level and is imported by setup.py, bootstrap.py and instance_setup.py(used by vcfg). instance_setup.py is the only file not at the same level as requirements.py, and it uses requirements.py only in specific use case(to install dependencies). Hence, moving the import of requirements.py into the specific function and explicitly updating sys.path within this function

@schandrika schandrika self-assigned this Feb 21, 2024
schandrika added a commit to schandrika/volttron that referenced this issue Feb 21, 2024
craig8 pushed a commit that referenced this issue Mar 25, 2024
craig8 added a commit that referenced this issue Mar 25, 2024
@craig8 craig8 closed this as completed Mar 25, 2024
craig8 added a commit that referenced this issue May 8, 2024
* Update readthedocs requirements.txt

* Update conf.py

* Update requirements_demo.txt

Add missing pandas requirement for demo

* work around for issue #3154

* Fix for security issue #3168 (#3169)

* Fix for security issue #3168

* handling clean up errors in test

* testing group commands in different test module

* moved group and role test to different module

* moved group and role test to different module

* Added a cache for agent names since platform start

* Fixes process overload from file events

* fixed issue with variable definition.

* Remove PersistentDict from web-user.json file.

* Update admin_endpoints.py

Handle behavior of removing PersistentDict

* Update version to 9.0.1

---------

Co-authored-by: Chandrika Sivaramakrishnan <chandrika@pnnl.gov>
Co-authored-by: Chandrika <schandrika@users.noreply.github.com>
Co-authored-by: Andrew Rodgers <andrew@aceiotsolutions.com>
@craig8 craig8 mentioned this issue May 8, 2024
14 tasks
craig8 added a commit that referenced this issue May 10, 2024
* Update readthedocs requirements.txt

* Update conf.py

* Update requirements_demo.txt

Add missing pandas requirement for demo

* work around for issue #3154

* Fix for security issue #3168 (#3169)

* Fix for security issue #3168

* handling clean up errors in test

* testing group commands in different test module

* moved group and role test to different module

* moved group and role test to different module

* Added a cache for agent names since platform start

* Fixes process overload from file events

* fixed issue with variable definition.

* Remove PersistentDict from web-user.json file.

* Update admin_endpoints.py

Handle behavior of removing PersistentDict

* Update version to 9.0.1

---------

Co-authored-by: Chandrika Sivaramakrishnan <chandrika@pnnl.gov>
Co-authored-by: Chandrika <schandrika@users.noreply.github.com>
Co-authored-by: Andrew Rodgers <andrew@aceiotsolutions.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants