ok, so there is no way to cache it and detect when the ref changes?
Yes, not sure it is connected either actually - To make it work, I had to disable both venv caching and set use_system_packages to off, so that it reinstalls the full env. I remember that we discussed this problem already but I don't remember what was the outcome, I never was able to make it update the private dependencies based on the version. But this is most likely a problem from pip that is not clever enough to parse the tag as a semantic version and check whether the installed package matches that version
yes, in setup.py I have:..., install_requires= [ "my-private-dep @ git+ ", ... ], ...
I mean the caching will work, but it will reinstall this repository on top of the cached copy.
make sense ?
Can you post them, I think there is something there that prevents the update (i.e. pip related).
For example:packagename @ git+https:///....Will be translated by pip to:
If packagename is installed do nothing, if it is not installed use git+https://... to install it
I update my-private-dep to 1.8.0
Not sure how this is connected with the venv, could you expand ?
replace it with:git+No need for the repository name, this will ensure you always reinstall it (again pip feature)
I call task._update_requirements(my_reqs) regardless whether I am in the local machine or in the clearml agent, so "installed packages" section is always updated to the list my_reqs that I pass to the function, in this case ["."]
JitteryCoyote63
Could you copy paste the "installed packages" section? the answer might be there