-
Notifications
You must be signed in to change notification settings - Fork 11
Tasks Troubleshooting
This is intended only for IVIS instance admins with direct access to the server.
In the /server/files/task-content
folder, there are folders with code and environment for all the tasks. Each task has its own separate folder marked by its ID. In the task folder, there is a dist
folder with the task code in job.py
and an env
folder with the Python virtual environment.
The setup of the virtual environment was run in a different directory and the libraries were copied here. So before one can activate the environment, it has to be re-initialized using /usr/bin/python3 -m venv env
. After that, one can activate the environment by running source env/bin/activate
and then install libraries and pip packages manually.
If one updates the code of the ivis
package and it does not update automatically in the task directory, it can be updated manually.
One should be able to initialize the update by running
pip install --no-index --upgrade --find-links="/ivis-core/server/lib/tasks/python/ivis" ivis
in the virtual environment with --find-links
set to correct path to the IVIS instance installation.
If that doesn't help, the files of the ivis
package can be manually copied to the directory as the package doesn't require any special installation. The code of the library can be found in /server/lib/tasks/python/ivis
. In the task virtual environment (env
directory), the library is saved in lib/python3.6/site-packages/ivis
(with possibly different version of Python than 3.6).