jupyter / jupyter/notebook

Download of notebooks as PDF is running into 500-Internal Server Error

Open
#6,296 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
13.3k
Forks
5.8k
Avg merge
6d 11h
Merged PRs (30d)
7

Description

Hello, the following issue describes the PDF via LaTeX Export of a notebook from jupyter which is running into an error.

**Describe the bug**
PDF via LaTeX Export of a notebook is running into 500-Internal Server Error.

**To Reproduce**
Steps to reproduce the behavior:
1. Create a simple Notebook
2. Fill a row with "print('hello')" out
3. Click on File -> Download as... -> PDF via LaTeX
4. See error (attaached to this issue)

**Expected behavior**
- Working PDF Export

**Screenshots**
see attached error message
[PDF-Export-Error.txt](https://github.com/jupyter/notebook/files/8177104/PDF-Export-Error.txt)
![Notebook-content](https://user-images.githubusercontent.com/76159512/156578737-e386c535-06ee-4c14-8ad6-1773a55fd401.PNG)

**Desktop**
- OS: any OS and any OS version
- Any browser and any browser versions

**Server Side**
- OS: Red Hat Enterprise Linux Server
- OS Version: 7.9 (Maipo)
- Patchlevel: latets
- Notebook server version: 6.0.3
- Python version: 3.7.6

Deeper investigation unfortunatly not possible. Thank you in advance for any advice and hint in resolution of that issue

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the File → Download as... → PDF via LaTeX workflow described in the issue, using the attached PDF-Export-Error.txt as the initial error evidence. Trace the server-side export failure and verify that the simple notebook produces a working PDF instead of a 500 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, latex, python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.