ipykernel restarting or failing on Mac M1.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- jupyter, jupyter-notebook, macos, python
- Domain
- operating-systems, tooling
Research direction
No repository file, test, or entry point is identified in the report. Start by reviewing the linked Jupyter Notebook and VS Code Jupyter reports, then obtain a reproducible ipykernel failure; done means isolating a specific Mac M1 failure case that can be addressed in this repository.
Written by the indexing model from the issue text.
Description
Hi,
The ipykernel restarting or failing on Mac M1.
HI since January I have experiecened that ipykernel keeps failing, randomly regardless what library or environment or python version or CPU arch I am using.
I tried in arm64/ x86_64. or python version 3.x.x.
I raised the issue in different related repos.:
jupyter/notebook repo:
https://github.com/jupyter/notebook/issues/6721
vscode/jjupyter repo:
https://github.com/microsoft/vscode-jupyter/issues/12775#issuecomment-1425506777
- Dominant language
- Python
- Stars
- 734
- Forks
- 411
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 9
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 ipython/ipykernel
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
ipython/ipykernel#1550 · 1 comment · 1 reaction · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
All issues in ipython/ipykernel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·