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
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Thanks Zach, it's probably because of the RTC: prefix of the custom YDrive. This has been a major source of issues, as a lot of JupyterLab extensions don't handle Jupyter drives, and even in JupyterLab core this is not a well supported feature.
In the long run, I think it will require making the JupyterLab default drive a proper drive. But we can fix this issue with the running panel before that.
Thanks @davidbrochart. That's right. We noticed the prefix isn't used when opening from the running panel.
Do we fix this in JupyterLab core now, in the running-extension? Or is this a Jupyter-collaboration plugin that replaces the necessary parts of the running-extension when RTC is enabled?
Description
If you click on the document in the "Running" panel, you will open a non-collaborative Notebook view.
Reproduce
Expected behavior
Opening a document from the "Running" panel should also open in collaborative model.
The text was updated successfully, but these errors were encountered: