posit-dev / posit-dev/positron
Occasional error when rendering quarto documents with the jupyter engine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
System details:
Positron and OS details:
Positron Version: 2025.04.0 (Universal) build 250
Code - OSS Version: 1.98.0
Commit: 627b3d723ee0b3a5bd86731a75902d419cafe22d
Date: 2025-04-03T16:31:38.728Z
Electron: 34.2.0
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Darwin arm64 24.4.0
Interpreter details:
Python 3.12.3
Describe the issue:
When attempting to render a qmd document using the jupyter engine from about 1 in 5ish of the times the following error will occur:
Starting python3 kernel...ERROR:
[Errno 2] No such file or directory: 'Lec25_stan.quarto_ipynb'
After the error it is possible to immediately attempt to re-render and the issue will go away and the document will successfully render.
This is a new issue with this release, using the same documents I was not seeing this behavior with the previous release.
Steps to reproduce the issue:
- Repeat a regular workflow with a jupyter qmd document and attempt to regularly re-render as you update the document.
Expected or desired behavior:
Were there any error messages in the UI, Output panel, or Developer Tools console?
Not that I can find
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.
Research direction
Start by repeatedly rendering a Jupyter-engine qmd document with Python 3.12.3 on Positron 2025.04.0, capturing the available Output panel and Developer Tools logs for failing and successful runs. The work is done when repeated renders no longer intermittently report the missing .quarto_ipynb file and the document renders successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, python
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100