Save button does not work. File system provider for vscode-interactive:Figure%201.png is not available.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- jupyter, jupyter-notebook, python, vscode
- Domain
- data-visualization, devtools
Research direction
No source file or test is identified in the issue. Start by reproducing the save-button failure in VS Code 1.63.2 with a Python script using %matplotlib ipympl, then trace the interactive figure's save path; done means the button saves the plot without the unavailable file-system-provider error and has regression coverage.
Written by the indexing model from the issue text.
Description
Each time I try to save a matplotlib plot generated by running a python script in an interactive window of Visual Studio Code 1.63.2 using %matplotlib ipympl , I get this error : "File system provider for vscode-interactive:Figure%201.png is not available."
The other buttons of the widget work fine.
3.8.12 (default, Oct 12 2021, 13:49:34)
[GCC 7.5.0]
ipympl version: 0.7.0
Selected Jupyter core packages...
IPython : 7.29.0
ipykernel : 6.4.1
ipywidgets : 7.6.5
jupyter_client : 6.1.12
jupyter_core : 4.9.1
jupyter_server : 1.4.1
jupyterlab : 3.2.1
nbclient : 0.5.3
nbconvert : 6.3.0
nbformat : 5.1.3
notebook : 6.4.6
qtconsole : 5.1.1
traitlets : 5.1.1
Known nbextensions:
config dir: /home/xavier/anaconda3/etc/jupyter/nbconfig
notebook section
jupyter-matplotlib/extension enabled
- Validating: OK
jupyter-js-widgets/extension enabled
- Validating: OK
JupyterLab v3.2.1
/home/xavier/anaconda3/share/jupyter/labextensions
jupyter-matplotlib v0.9.0 enabled OK
@jupyter-widgets/jupyterlab-manager v3.0.0 enabled OK (python, jupyterlab_widgets)
- Dominant language
- Jupyter Notebook
- Stars
- 1.7k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from matplotlib/ipympl
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
matplotlib/ipympl#623 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
matplotlib/ipympl#622 · 13 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
matplotlib/ipympl#612 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
matplotlib/ipympl#611 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
matplotlib/ipympl#609 · 6 comments ·
All issues in matplotlib/ipympl
Similar issues
-
Urgent request: Due to vulnerabilities move to API version 12.6.1 (12.6.2 eventually) or 13.1.1 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
jbkunst/highcharter#849 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AOSSIE-Org/OrgExplorer#245 · 1 assignee ·
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gordonwatts/test-wsl2-llm#151 ·