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, I Think I Found A Problem With A Clean Clearml Install. I Create A New Python Env:

Hi, I think I found a problem with a clean clearml install.

I create a new python env:

conda create -n py310 python=3.10

pip install clearml

python -c "import clearml"

Traceback (most recent call last):
File "/home/luis/miniconda3/envs/py310/lib/python3.10/site-packages/clearml/utilities/requests_toolbelt/_compat.py", line 48, in <module>
from requests.packages.urllib3.contrib import appengine as gaecontrib
ImportError: cannot import name 'appengine' from 'requests.packages.urllib3.contrib' (/home/luis/miniconda3/envs/py310/lib/python3.10/site-packages/urllib3/contrib/init.py)

the urllib3 version installed automatically was:
urllib3 2.0.2

and I check on their github that (update was a couple of days ago) 'appengine' has disappeared from 'contrib' from version 2.x onwards.

Anybody reproducing this? Maybe clearml pin the urllib requirement?

edit: forcing urllib3 < 2, it works

  
  
Posted one year ago
Votes Newest

Answers 6


@<1541954607595393024:profile|BattyCrocodile47> yeah, we removed that specific dependency in the RC (we don't really use that part) and will release a new version soon 🙂

  
  
Posted one year ago

Hi @<1523701070390366208:profile|CostlyOstrich36> , that solves the problem!

  
  
Posted one year ago

Hi @<1534344465790013440:profile|UnsightlyAnt34> , try installing clearml==1.10.4rc1

  
  
Posted one year ago

I literally just ran into this minutes ago and was about to file a bug report. A colleague ran into the same problem. It looks like urllib3 upgraded to v2 last week.

  
  
Posted one year ago

when can we expect an 1.10.4 release ; ) ?

  
  
Posted one year ago

Another workaround that did the trick for me was to fix the version of urllib3 in your requirements.txt
urllib3==1.26.15

  
  
Posted one year ago
947 Views
6 Answers
one year ago
one year ago
Tags