Doesn't currently build on MyBinder
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- jupyter
- Domain
- build-system, devops
Research direction
Start from the Launch Binder badge in the repository README and inspect the .binder/postBuild command shown in the failure log. Reproduce the build and investigate why /home/jovyan/ipympl/package.json is missing when the JupyterLab extension is built. Done means the Binder build completes successfully from the linked badge.
Written by the indexing model from the issue text.
Description
Issue
What is linked from launch badge in Readme doesn't currently build on MyBinder
It seems it isn't properly seeing package.json for some reason..
Steps to reproduce
Go to the main repo Readme page here and click the launch binder badge.
The end of a build example that fails is shown below (... on first line represents start of the log that is not shown):
...
Successfully installed ipympl-0.8.7 ipywidgets-7.7.5 jupyterlab-widgets-1.1.4 widgetsnbextension-3.6.4
Remote version of pip: 23.1.2
Local version of pip: 23.0.1
Was pip installed by pip? False
Removed build tracker: '/tmp/pip-build-tracker-zn9i3t0k'
/srv/conda/envs/notebook/lib/python3.10/site-packages/setuptools/config/setupcfg.py:516: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
warnings.warn(msg, warning_class)
Installing /home/jovyan/ipympl/labextension -> jupyter-matplotlib
Building extension in /home/jovyan/ipympl
An error occurred.
FileNotFoundError: [Errno 2] No such file or directory: '/home/jovyan/ipympl/package.json'
See the log file for details: /tmp/jupyterlab-debug-22xaku6u.log
Removing intermediate container 9dfca785e89e
The command '/bin/sh -c ./.binder/postBuild' returned a non-zero code: 1
- 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
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
Builders
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100