Incompatibility (?) with jupyterlab 4.x
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I have noticed the proble with the conda-forge install of jupyterhub+jupyterlab+ipykernel+ipyflow (large but fairly standard install). After installing of ipyflow some (not all!) notebooks stop responding to Ctrl+Enter and "run cell" buttons. This is also for notebooks running ipykernel! Just installing ipyflow triggers this behaviour. I have verified it also on standalone conda-forge install (just jl+ipyk+ipyflow). This is really unfortunate. I had to remove ipyflow from the install due to the fact that it affects non-users. I have no clue what is the reason and real trigger but I can run some experiments if necessary.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the issue with the standalone conda-forge JupyterLab, ipykernel, and ipyflow installation described in the report, then compare notebooks that respond and do not respond to Ctrl+Enter or the run-cell buttons. Done means identifying the trigger and preventing ipyflow from disrupting affected notebooks, including notebooks running ipykernel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, python
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100