thanks!

AgitatedDove14 same thing happens to me when I run via git bash

I can also send you a link to the task this created on our hosted allegro web server, to look at the logs, if that helps

I did not start with python -m, as a module. I'll try that

I do not think this is the issue.
It sounds like anything you do on your specific setup will end with the same error, which might point to a problem with the git/folder ?

😞 It's working as expected for me...
That said I tested on Linux & pip,
Any specific req to test with? from the log I see this is conda on windows, are you using the base conda env or a venv inside conda?

I'm having some issues with my github access, I'll guess I'll update later/tomorrow when I solve them

same same. I ran inside clearml git repo and got the same warnings

Sure thing, let me know ... 🙂

ThickDove42 Windows conda python3.6 was exactly what I was using,
started the jupyter with:
"python -m jupyter notebook"
Then opened / created a new notebook, everything worked.
Tested on latest clearml 0.17.2
Maybe it's something with the path to the repo that breaks it? Because obviously the issue is it is looking in the wrong folder.

btw, I see the same thing when I start the notebook directly, i.e. "jupyter notebook path/to/notebook.ipynb" and when I start the notebook server "jupyter notebook" and then open the notebook from the jupyter web interface.

in the mean time, I installed a new clean virtualenv (no conda) and got the exact same behavior. I'll try running as a module and we'll see

ok, that's a difference, I did not start with python -m, as a module. I'll try that

but this gives me an idea, I will try to check if the notebook is considered as trusted, perhaps it isn't and that causes issues?

This is exactly what I was thinking (communication with the jupyter service is done over http, to localhost, sometimes AV/Firewall software will block it, false-positive detection I assume)

ok got it. Moshik just sent me a snippet that identified that this is indeed the problem. I will try to see if I can setup an exception. that may prove tricky since that's the IT control

AgitatedDove14 - nailed it! it was due to my notebook being pwd protected rather than token protected. I shared that with Moshik. I wonder whether that could be worked around.

Nice! I'll see if we can have better error handling for it, or solve it altogether 🙂

create a notebook, add the following lines to it's first cell:
from clearml import Task task=Task.init(project_name='proj', task_name='notebook', task_type=Task.TaskTypes.custom, continue_last_task=True,)run the cell

I'll try running using gitbash, perhaps it would work better, although I use the same conda env when I run scripts from pycharm, or from the windows cmd

I'm on windows, this is a python 3.6 conda venv, I think you can see the name of the env in the logs...

ThickDove42 Windows also works 😞
Any specifics on the setup?

How can I reproduce it?

Okay Let me check

AgitatedDove14 I don't understand how that's related. I am working on localhost, why should I have a problem communicating with the jupyter server? It's local. Also, the kernel has no problem communicating with the allegro server, obviously (since results are logged).

but this gives me an idea, I will try to check if the notebook is considered as trusted, perhaps it isn't and that causes issues?

ThickDove42 looking at the code, I suspect it fails interacting with the actual jupyter server (that is running on the same machine, but still).
Any chance you have a firewall on the Windows machine ?

What's the jupyter / noetbook version you have?
Also from within the jupyter could you send me "sys.argv" ?

(and as you said, running as a module didn't change anything)

You can try calling
task._update_repository()I'm still trying to figure out how to reproduce it...

Could you try to clone the clearml git repo, create a new notebook in it and test ?

AgitatedDove14 is there some way I can update the script file manually and retrigger the git discovery process?

sure