Hi GentleSwallow91 , I would highly recommend upgrading to 1.9 as it brings new also a new major feature (as well as minor bug fixes). I'm not sure about DB migration - there might be one or two. I suggest taking a look at the versions in between 🙂
Hi GentleSwallow91 , no major migration between either of these versions - should be fully automatic, just make sure you're using the latest docker-compose.yaml file, pull the images and you should be good to go 🙂
Thanks @<1523701087100473344:profile|SuccessfulKoala55>
I've looked into the docker-compose and found a new image async_delete
Not sure what it does and if I should include it into upgraded installation.
If I do - there is a parameter CLEARML__services__async_urls_delete__fileserver__url_prefixes: "[${CLEARML_FILES_HOST:-}]"
I guess I should set it to fileserver in case of one docker-compose?
Made an upgrade to the latest version from 1.5 and have stumbled upon an issue with webserver:
I am saving all artefacts to a custom s3 server. Used to work fine - saving and downloading them from webserver. Now I can now download anything that resides on s3 - getting the following errors in browser console:
Unable to parse "https None " as a whatwg URL.
ERROR EndpointError: Custom endpoint https [None](//storage.yandexcloud.net) was not a valid URI
Back at 1.5 there was an issue with custom s3 endpoints - to treat those as custom one needed to specify a port at the end - even it it is 443 - maybe that's the case?
there is a parameter
CLEARML__services__async_urls_delete__fileserver__url_prefixes: "[${CLEARML_FILES_HOST:-}]"
I guess I should set it to
fileserver
in case of one docker-compose?
I think you can just leave it as-is
The webapp error seems to be coming from the AWS JS packages used for accessing s3-stored resources... Can you share an example of the s3 file references? Obviously these would not start with https ...?
Hi @<1523701366600503296:profile|GentleSwallow91>https None is not a valid URL.
you're missing a colon : after https
it might be a bug we already fixed, let me check
the bug is during creation of S3 bucket credential creation. you can manually fix the URL in settings -> Configuration
under WEB APP CLOUD ACCESS find the right Host (Endpoint) field and add the missing colon.
we will release a fix to 1.9 soon.
Thanks @<1523703436166565888:profile|DeterminedCrab71>
I've tried that - it does not work - I have a valid endpoint in settings but a missing colon in js console
Waiting for a fix 🙏
Hi! any update on that fix? @<1523703436166565888:profile|DeterminedCrab71>
maybe it is not present in 1.8 and will just use that version?
1.9.2 with a fix should be released, I think today, let me check
I was just informed that the images for 1.9.2 were already released on Thursday, please test if the new version solve the issue for you and let us know.
ClearML is awesome - all works fine now! Will test the rest.