Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hello Folks! I'Ve Deployed Clearml, Helm Chart Version

Hello Folks! I've deployed ClearML, helm chart version 7.11.1 , on a k8s cluster. I've created ingresses for all three api , web and file servers. I'm trying to upload images to my experiment via logger.report_media method, however, when i debug samples for the experiment, i see the following issue: (SEE Attachment)
Has anyone seen this before? Any idea how to fix this?
image

  
  
Posted 4 months ago
Votes Newest

Answers 12


It looks something like this:

.<redacted>/ClearML_POC/exp2_reporting.705a68df922d46c3848e679774faac5e/metrics/test2/test/test2_test_00000001.png?X-Amz-Date=1722509256352
  
  
Posted 3 months ago

Any feedback in how to solve this would be really appreciated! This is currently the only barrier in our way to adopt ClearML

  
  
Posted 3 months ago

The address is valid. If i just go to the files server address on my browser,

@<1729309131241689088:profile|MistyFly99> what is the exact address of those files? (including the http prefix) and what is the address of the web application ?

  
  
Posted 3 months ago

and this link on it's own works?
if it does, open your browser dev tools (ctrl+shift+I on chrome, I think), I'm assuming you will see a few errors on CORS or the alike, paste them here

  
  
Posted 3 months ago

The network tag of dev tools shows this, but there is nothing like CORS being reported in the browser console. This link on its own does not work but the fileserver domain is working and shows an OK message
image
image

  
  
Posted 3 months ago

@<1523701070390366208:profile|CostlyOstrich36> @<1523701087100473344:profile|SuccessfulKoala55>

  
  
Posted 3 months ago

Yes! This was the magic sauce! Thank you so much @<1523701087100473344:profile|SuccessfulKoala55> ! Really appreciate it

  
  
Posted 3 months ago

I saw that there have been similar issues but the resolution wasn't clear. In our case, https works perfectly but the media retreival is running into 401s
image
image

  
  
Posted 3 months ago

It's seems you are are getting 401 unauthorized , is this the same domain? I'm assuming the issue the logged in cookie is not sent?

  
  
Posted 3 months ago

Hi @<1729309131241689088:profile|MistyFly99>
notice that the files server need to have an "address" that can be accessed from the browser, data is stored in a federated manner. This means your browser is directly accessing the files server, not through the API server, I'm assuming the address is not valid?

  
  
Posted 4 months ago

Hello @<1523701205467926528:profile|AgitatedDove14> ! The address is valid. If i just go to the files server address on my browser, i can see OK . I tried it with both, port forwarding from the service directly, as well as using a file.*.* ingress host, but no joy 😞

  
  
Posted 3 months ago

Hi @<1729309131241689088:profile|MistyFly99> , please see here:
None
I think this is exactly the issue you're experiencing

  
  
Posted 3 months ago