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
Hi Everyone, I Have A Question. I Have Deployed The Clearml Server Behind A Load Balancer That Is Using My Company’S Private Certificate For Ssl. Now, When I Try To Execute A Task With The Clearml Sdk I Get Errors Such As:

hi everyone,
I have a question. I have deployed the ClearML server behind a load balancer that is using my company’s private certificate for SSL.
Now, when I try to execute a task with the clearml sdk I get errors such as:
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)

To solve it, for now, I have adjusted my clearml.conf with verify_certificate: False

api {
    web_server: 

    api_server: 

    files_server: 

    credentials {
        "access_key" = "xxx"
        "secret_key"  = "yyy"
    }
    verify_certificate: False
}

so now when I try to run Task.init(…) it works.

But, when I try to run Dataset.create(…) then again I get the same SSL error. Why requests from the Dataset method to the file server still give this error, and is there a configuration change that can skip SSL check for now?

  
  
Posted 5 months ago
Votes Newest

Answers 2


it’s executed on the same agent machine, so yes, it is the same configuration

  
  
Posted 5 months ago

The dataset call should use the same configuration from the conf file, I assume it's the same, or are you running it from a different place?

  
  
Posted 5 months ago