Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback from Jupyter notebook extension early adopters #113245

Closed
14 of 42 tasks
rebornix opened this issue Dec 21, 2020 · 7 comments
Closed
14 of 42 tasks

Feedback from Jupyter notebook extension early adopters #113245

rebornix opened this issue Dec 21, 2020 · 7 comments
Assignees
Labels
notebook under-discussion Issue is under discussion for relevance, priority, approach

Comments

@rebornix
Copy link
Member

rebornix commented Dec 21, 2020

We have received hundreds of good feedbacks from early adopters of the Jupyter extension using native notebook support. The clean UX, seamless integration with VS Code ecosystem and improved performance are mostly loved. However we are also seeing bugs and UX issues users are struggling with. Here I tried to compile the feedbacks into issues so we can track where we are with them.

Bugs & UX improvements

Core

Jupyter

Feature Requests

Core

Jupyter

@rebornix rebornix added notebook under-discussion Issue is under discussion for relevance, priority, approach labels Dec 21, 2020
@hugocool
Copy link

Im on Version: 1.53.0-insider
When using plotly with vscode renderer (to which the renderer is set by default) I get an error:
No renderer could be found for MIME type: application/vnd.plotly.v1+json

@DonJayamanne
Copy link
Contributor

Need more info for the following to understand the issue:

  • Kernel -> could get kernel to connect
  • Kernel -> severe performance issues. appears to degrade over time, requiring regular restarts of the kernel
  • The linter often gets stuck
  • Renderer
    • Plots with all content outside the axes (i.e., tick labels, etc.) shaded such that they are difficult to read.
    • Screen shot with sample code would help.

Info related to some of the issues reported above:

@claudiaregio
Copy link

@rebornix Additional feedback has come in since this issue was created and want to make sure we are also capturing the cell execution hanging and the interrupt cell execution also not working

@claudiaregio
Copy link

Created issue but realized it was mentioned here.

  • Cell/output collapse

    • When dealing with cells containing very long output is quite clunky, you can right click on the cell and collapse output, but then it's fully collapsed and you don't see anything
    • Collapsing a very long cell when you're looking at its end, the document scroll position should probably jump to the code cell that produced the collapsed output: Native Notebooks - Collapsing output from bottom leads to incorrect scroll location #114866
    • Show the first line when a cell is collapsed

@ghost
Copy link

ghost commented Apr 5, 2021

@rebornix Can the vscode team please reconsider menu contributions?

There are lots of issues with complaints about users being forced to have jupyter installed with the python extension, and msft's python/jupyter extension team ignores feedback and users complaints and quickly shuts down any discussion unless it's from a vscode team member.

@miguelsolorio
Copy link
Contributor

@rebornix I think this issue is a bit outdated, leaving for you to decide if you want to keep it open.

@miguelsolorio miguelsolorio removed their assignment Oct 6, 2021
@rebornix rebornix closed this as completed Dec 3, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jan 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
notebook under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

6 participants
@rebornix @DonJayamanne @claudiaregio @hugocool @miguelsolorio and others