Jupyterlab Nsight plugin breaks when running Jupyterlab in any directory other than "."

Developer Tools Nsight Systems Profiling Linux Targets
1

Hi, the Nsight Plugin for JupyterLab breaks when Jupyterlab is launched in any directory other than “.”
A really simple reproduce case is this:

  1. Set up clean Python environment and install jupyterlab
python3 -m venv .venv
source .venv/bin/activate
pip3 install jupyterlab torch jupyterlab-nvidia-nsight nvtx
  1. Create a test directory
mkdir test
  1. Run jupyterlab while passing a directory (in this case I’m passing “…”)
cd test
jupyter lab ..
  1. In the UI navigate to the “test” directory.
  2. Create a new notebook
  3. Enable profiilng using the plugin (either Nsight Systems or Nsight Compute)
  4. Profile a simple operation that uses the GPU, e.g
import torch
a = torch.randn([1024,1024], device='cuda')
a @ a

This should fail for both Nsight Systems and Nsight Compute profiling. The cell will be profiled, but then the file will not be copied to the correct location. You can still find the file in /tmp/, but this is difficult to do (more so for Nsight Compute, less so for Nsight Systems).

The bug is that it doesn’t take into account the directory where jupyter lab was launched. E.g. it works when running with “jupyter lab .” instead of “jupyter lab …”

Since you will often want to pass this argument (e.g. if you want to keep the installation of jupyterlab separate from your normal working directory), and since it’s a normal argument to jupyterlab, I think this should be supported.

2

@dofek can you have someone fix this.

Thank you for the very thorough report!

3

Thank you, @far.tea4870 for reporting this issue. The upcoming version of the extension will contain a fix.

4

jupyterlab-nvidia-nsight 0.7.0 is released and containing the fix.
@far.tea4870 FYI