There could be a few things. The notebook path goes through a symlink a few levels up the file system (before hitting the repo root, though). I'm also in an anaconda env with a mix of conda and pip packages. The notebook kernel is also not the default kernel, but that's a common use case.
If it helps to know, I'm running on Linux with jupyterlab, and the trains-server is hosted on the same machine (using the defaults from the docker-compose.yml ). I'm on trains version 0.16.3 .
SmugDog62 so on plain vanilla Jupyter/lab everything seems to work.
What do you think is different in your setup ?
The notebook path goes through a symlink a few levels up the file system (before hitting the repo root, though)
Hmm sounds interesting, how can I reproduce it?
The notebook kernel is also not the default kernel,
What do you mean?
Hi SmugDog62
My guess is that there's an issue with the git repo detector.
Seems like you are correct
Can are you getting on the execution tab?
Is the repo correct?
Do you see the notebook in the uncommited changes ?
I checked the execution tab, but no repo information is listed. The "Source Code" table looks like:REPOSITORY origin COMMIT ID SCRIPT PATH ipykernel_launcher.py WORKING DIRECTORY .
The "Uncommitted Changes" info is just the " Entry point for launching an IPython kernel." script, which I believe is boilerplate from trains. There's no mention of my specific notebook code.