Is this a possible future feature? I have used cometML before and they have this. I'm not sure how they do it though...
but it's been that way for over 1 hour.. I remember I can force the task to wait for the upload. how do i do this?
well.. it initially worked but now i get the same thing 😕 SuccessfulKoala55
i don't think the conf is an issue. it's been deployed for a long time and working. models from yesterday correctly display the url
I think the issue is that the host is not trusted... it looks like it looks into the index
so it tries to find it under /usr/bin/python/
I assume?
I think it's still caching environments... I keep deleting the caches (pip, vcs, venvs-*) and running an experiment. it re-creates all these folders and even prints
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.8/dist-packages (from requests>=2.20.0->clearml==1.6.4->prediction-service-utilities==0.1.0) (3.4)
Requirement already satisfied: charset-normalizer<4,>=2 in /root/.clearml/venvs-builds/3.8/lib/python3.8/site-packages (from requests>=2.20.0->clearml==1.6....
I understand! this is my sysadmin message:
"if nothing else, they could publish a new elasticsearch image of 7.6.2 (ex. 7.6.2-1) which uses a newer patched version of JDK (1.13.x but newer than 1.13.0_2)"
can you elaborate a bit on the token side? i'm not sure exactly what would be a bad practice here
hi SuccessfulKoala55 ! has the docker compose been updated with this?>
In fact I just did that yesterday. I'll let you know how it goes
"this means the elasticsearch feature set remains the same. and JDK versions are usually drop-in replacements when on the same feature level (ex. 1.13.0_2 can be replaced by 1.13.2)"
hi SuccessfulKoala55 with the clearml server update, does it use a newer ES docker?
Ok, going to ask the server admins, will keep you posted, thanks!
Not sure why it tries to establish some http connection, or why it's /
...