Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't export using nbconvert: `Export failed. Please check the 'Jupyter' output panel for further details`

See original GitHub issue

Environment data

VS Code version: Version: 1.62.0-insider (user setup) Commit: dc1a6699060423b8c4d2ced736ad70195378fddf Date: 2021-10-26T08:49:04.076Z Electron: 13.5.1 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.22483
Jupyter Extension version (available under the Extensions sidebar): v2021.10.1001384888
Python Extension version (available under the Extensions sidebar): v2021.10.1365161279
OS (Windows | Mac | Linux distro) and version: Windows 11
Python and/or Anaconda version: Python 3.9.7
Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
Jupyter server running: Local

Expected behaviour

Testing https://github.com/microsoft/vscode/issues/135666

Switch to nbconvert export setting (already successfully used other 2 export settings)
… -> Export -> Python Script
Screenshot 3 in test plan item

Actual behaviour

🐛 Export failed. Please check the 'Jupyter' output panel for further details.

Jupyter output panel

Logs here: Jupyter output.txt.

Additional info

I started my testing with the same exact cells pictured in the test plan item screenshots
I tried other notebooks, and they fail with the same message
When I try exporting with nbconvert setting again, it still fails each time

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

IanMatthewHuffcommented, Oct 27, 2021

@rchiodo Yeah, we had guards around all the nbconvert required areas in the old UI. Looks like the new UI exposed a new code path here that doesn’t have that check. Given that we’re still surfacing ‘nbconvert’ as an option we should fix but doesn’t seem Endgame worthy at all.

0reactions

DonJayamannecommented, Dec 1, 2021

Verified, but subsequent exports will never get the prompt (if i don’t select an interpreter the first time). Created separate issue for that.