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

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

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

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.

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

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

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?

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.

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

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