You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some situations this extension results in showing a dialog "Error: Repository is read only" if one wants to create a new "Untitled.ipynb" notebook by clicking in the launchpad on "Python 3".
As soon as one has interacted with the filebrowser in some way, like creating a new file for example, this problem does not occur anymore. So I assume that the function "newUntitled" of the file-browser-plugin is called when a "Python 3"-notebook is newly created. And somehow the implementation of JupyterLab-GitLab is first in the row - which should not be the case.
I have seen this in JupyterLab 3.6 and now also in 4.2.1.
The text was updated successfully, but these errors were encountered:
The current work-around:
If you want to create a new notebook directly after restarting JupyterLab and do not want to open an existing one, you have to use the context menu of the file browser and not the buttons in the launchpad:
In some situations this extension results in showing a dialog "Error: Repository is read only" if one wants to create a new "Untitled.ipynb" notebook by clicking in the launchpad on "Python 3".
I assume it comes from this lines of code:
https://github.com/jupyterlab-contrib/jupyterlab-gitlab/blob/main/src/contents.ts#L321
As soon as one has interacted with the filebrowser in some way, like creating a new file for example, this problem does not occur anymore. So I assume that the function "newUntitled" of the file-browser-plugin is called when a "Python 3"-notebook is newly created. And somehow the implementation of JupyterLab-GitLab is first in the row - which should not be the case.
I have seen this in JupyterLab 3.6 and now also in 4.2.1.
The text was updated successfully, but these errors were encountered: