
Reputation
Badges 1
123 × Eureka!I also see that elastisearch and mongo has some data
When I look at LinkEntry object, link property is correct, no duplicates. Its relative_path thats duped and also key name in _dataset_link_entries
I also dont have side panel for some reason
@<1523701435869433856:profile|SmugDolphin23> Any ideas how to fix this?
How can I do that?
I need to save the original hash, otherwise I lose all trackability to about 2k experiments
The problem is that clearml.conf s3 config doesnt support empty region field, even empty strings crashes it
This is what I see on fresh clearml
Where all my mounts are on /mnt/data/clearml-server instead of /opt/clearml
is there any way to see if I even have the data in mongodb?
I already found the source code and i modified it as needed.
How can I now get this info from Task that is created when Dataset is created?
Couldnt find anything like clearml.Dataset(id=id).get_size()
@<1523701070390366208:profile|CostlyOstrich36> 👀
good morning, I tried the script you provided and Im getting somewhere
py file:
task: clearml.Task = clearml.Task.init(
project_name="project",
task_name="task",
output_uri=" None ",
)
clearml.conf:
{
# This will apply to all buckets in this host (unless key/value is specifically provided for a given bucket)
host: " our-host.com "
key: "xxx"
secret: "xxx"
multipart: false
...
there is a typing in clearm.conf i sent you on like 87, there should be "key" not "ey" im aware of it
I know these keys work, url and everything else works because I use these creds daily
I get sidebars and login on my local PC
But the data isnt loaded
I tried to not edit anything in docker-compose and just paste my data in there. Didnt help
Is is even known if the bug is fixed on that version?
here is also another magic stuff
I guess I fucked up something when moving files
Hey, i see that 1.14.2 dropped
I tried it but the issue is still there, maybe the hotfix is in next patch?
Here is the setup so you can reproduce it (we dont have region field)
clearml.conf:s3 {
use_credentials_chain: false
credentials: [
{
host: "
s3.somehost.com "
key: "XXXXXXXXXXXXXXXXXXXX"
` secret: "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...