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
Hello! I'M Just Starting Out With Clearml, And I Seem To Be Having Some Sort Of Conflict Between

Hello! I'm just starting out with ClearML, and I seem to be having some sort of conflict between clearml and torch , at least in Colab

In this guide ( https://huggingface.co/blog/how-to-train ), I added a section at the top like so:
!pip install clearml from clearml import Task task = Task.init(project_name="project name", task_name="Esperanto_Bert")
But then later, when I attempt to import torch , I get errors, see attached screenshot

When I run the same notebook without trying to install/use clearML, I get no issues.

Any advice?

Posted 2 years ago
Votes Newest

Answers 10

Hi SmallDeer34
Can you try with the latest RC , I think we fixed something with the jupyter/colab/vscode support
!pip install clearml==1.0.3rc1

Posted 2 years ago

One additional question, if you import clearml after you call torch does it work ?

Posted 2 years ago

OK, so with the RC, the issue has gone away. I can now import torch without issue.

Posted 2 years ago

I will test both! Thanks for the ideas!

Posted 2 years ago


Posted 2 years ago

But then I took out all my additions except for pip install clearml and
from clearml import Task task = Task.init(project_name="project name", task_name="Esperanto_Bert_2")and now I'm not getting the error? But it's still install 1.02. So I'm just thoroughly confused at this point. I'm going to start with a fresh cop of the original colab notebook from https://huggingface.co/blog/how-to-train

Posted 2 years ago

I think this is somehow related to the JIT compiler torch is using.
My suspicion is that JIT cannot be initialized after something happened (like a subprocess, or a thread).
I think we managed to get around it with 1.0.3rc1.
Can you verify ?

Posted 2 years ago

SmallDeer34 No worries, I'm happy to hear the issue disappeared 🙂

Posted 2 years ago

Did a couple tests with Colab, moving the installs and imports up to the top. Results... seem to suggest that doing all the installs/imports before actually running the tokenization and such might fix the problem too?

It's a bit confusing. I made a couple cells at the top, like thus:
!pip install clearmland
from clearml import Task task = Task.init(project_name="project name", task_name="Esperanto_Bert_2")and
# Check that PyTorch sees it import torch torch.cuda.is_available()and
` # We won't need TensorFlow here
!pip uninstall -y tensorflow

Install transformers from master

!pip install git+
!pip list | grep -E 'transformers|tokenizers'

transformers version at notebook update --- 2.11.0

tokenizers version at notebook update --- 0.8.0rc1 `and it seems that no matter what order I run them in, I don't get an error. This is complicated by the fact that I'm trying to get Colab to give me a clean runtime each time but I'm having some odd issues with that.

So I wonder if it's got something to do with not just the installs but all the other imports along the way, e.g. importing the tokenizer object and so forth?

Posted 2 years ago

Sure, I don't seem to be having any trouble with 1.03rc1. As for 1.02, like I said, the original issue seems to have mysteriously gone away, like some sort of heisenbug that goes away when I mess with the Notebook.

With a completely fresh notebook I added the cells to install clearml 1.02 and initiate a Task, and ran the notebook again, and... the issue seems to have disappeared again.

Not sure how to even replicate the original issue anymore, sorry I couldn't be of more help!

Posted 2 years ago
10 Answers
2 years ago
one year ago