docs/source/getting_started/issue.md
% Copyright (c) Jupyter Development Team.
% Distributed under the terms of the Modified BSD License.
(issue)=
Thank you for providing feedback about JupyterLab.
If you find a problem in JupyterLab, please follow the steps below to diagnose and report the issue. Following these steps helps you diagnose if the problem is likely from JupyterLab or from a different project.
Try to reproduce the issue in a new environment with the latest official JupyterLab installed and no extra packages.
If you are using conda:
create a new environment:
conda create -n jlab-test --override-channels --strict-channel-priority -c conda-forge -c nodefaults jupyterlabActivate the environment:
conda activate jlab-testStart JupyterLab:
jupyter lab
Perhaps the issue is in one of the JupyterLab extensions you had installed. Install any JupyterLab extensions you had one at a time, checking for the issue after each one.
create-issue.Try to reproduce the issue in the classic Jupyter Notebook. Launch the classic notebook from the JupyterLab help menu to ensure you are getting exactly the same notebook server that JupyterLab is using.
Try to reproduce the issue in your browser incognito or private browsing mode. Running in private browser mode ensures your browser state is clean.
create-issue.You might also check your system for:
(create-issue)=
Before creating an issue, search in the issue tracker for relevant issues. If you find an issue describing your problem, comment there with the following information instead of creating a new issue. If you find a relevant resolved issue (closed and locked for discussion), create a new issue and reference the resolved issue.
To create an issue, collect the following contextual information:
relevant package versions, including:
jupyterlab and notebook versionsrelevant server and JavaScript error messages
screenshots or short screencasts illustrating the issue
Create a new issue. Include the contextual information from above. Describe how you followed the diagnosis steps above to conclude this was a JupyterLab issue.
Communication in JupyterLab follows the Jupyter Community Guides.