hello.ipynb File gets JSON Error

[MLHaasch]

What would you like to do?

Report an issue on quarto.org

Description

When trying to Preview or Render the hello.ipynb file on my MacBook Pro (Apple M1 Pro; Sequoia 15.2, Safari 18.2 (20620.1.16.11.8)

Hello-ipynb_TextEdit.docx

) the following error is displayed.
ERROR: SyntaxError: Unexpected token 'b', "bookma"... is not valid JSON

Stack trace:
at JSON.parse ()
at Object.markdownForFile (file:///Applications/quarto/bin/quarto.js:40115:29)
at mdForFile (file:///Applications/quarto/bin/quarto.js:39911:29)
at projectResolveFullMarkdownForFile (file:///Applications/quarto/bin/quarto.js:39992:26)
at Object.resolveFullMarkdownForFile (file:///Applications/quarto/bin/quarto.js:90464:20)
at fileExecutionEngineAndTarget (file:///Applications/quarto/bin/quarto.js:41550:36)
at async renderContexts (file:///Applications/quarto/bin/quarto.js:80376:32)
at async renderFormats (file:///Applications/quarto/bin/quarto.js:80421:22)
at async file:///Applications/quarto/bin/quarto.js:107988:24
at async Command.actionHandler (file:///Applications/quarto/bin/quarto.js:107985:25)
mary.haasch@KWH600DK6G QuartoProject % python3 -m jupyter lab hello.ipynb
usage: jupyter.py [-h] [--version] [--config-dir] [--data-dir] [--runtime-dir] [--paths] [--json] [--debug] [subcommand]

Jupyter: Interactive Computing

positional arguments:
subcommand the subcommand to launch

options:
-h, --help show this help message and exit
--version show the versions of core jupyter packages and exit
--config-dir show Jupyter config dir
--data-dir show Jupyter data dir
--runtime-dir show Jupyter runtime dir
--paths show all Jupyter paths. Add --json for machine-readable format.
--json output paths as machine-readable json
--debug output debug information about paths

Available subcommands:

Jupyter command jupyter-lab not found.

[mcanouil]

Why did you open a documentation issue? As is there is pretty much nothing we can do to help.
Did you install all required dependencies as described in the documentation? Are you using the latest version of Quarto CLI?
What's the docx file you attached?

Could you properly format your post using code blocks for code and terminal outputs? Thanks.
If your code contains code blocks, you need to enclose it using more backticks, i.e., usually four ````.
See https://quarto.org/bug-reports.html#formatting-make-githubs-markdown-work-for-us.

Could you share a small self-contained "working" (reproducible) example to work with, i.e., a complete Quarto document or a Git repository? The goal is to make it as easy as possible for us to recreate your problem so that we can fix it: please help us help you! Thanks.

---

You can share a self-contained "working" (reproducible) Quarto document using the following syntax, i.e., using more backticks than you have in your document (usually four ````).
See https://quarto.org/bug-reports.html#small-is-beautiful-aim-for-a-single-document-with-10-lines.

If you have multiple files (and if it is absolutely required to have multiple files), please share as a Git repository.

R	Python
````qmd --- title: "Reproducible Quarto Document" format: html engine: knitr --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{r} x <- c(1, 2, 3, 4, 5) y <- c(1, 4, 9, 16, 25) plot(x, y) ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````	````qmd --- title: "Reproducible Quarto Document" format: html engine: jupyter --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{python} import matplotlib.pyplot as plt x = [1, 2, 3, 4, 5] y = [1, 4, 9, 16, 25] plt.plot(x, y) plt.show() ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````

Additionally and if not already given, please share the output of quarto check within a code block (i.e., using three backticks ```txt), see https://quarto.org/bug-reports.html#check.

[MLHaasch]

Why did you open a documentation issue? As is there is pretty much nothing we can do to help. Did you install all required dependencies as described in the documentation? Are you using the latest version of Quarto CLI? What's the docx file you attached?

Could you properly format your post using code blocks for code and terminal outputs? Thanks. If your code contains code blocks, you need to enclose it using more backticks, i.e., usually four ````. See https://quarto.org/bug-reports.html#formatting-make-githubs-markdown-work-for-us.

Could you share a small self-contained "working" (reproducible) example to work with, i.e., a complete Quarto document or a Git repository? The goal is to make it as easy as possible for us to recreate your problem so that we can fix it: please help us help you! Thanks.

You can share a self-contained "working" (reproducible) Quarto document using the following syntax, i.e., using more backticks than you have in your document (usually four ````). See https://quarto.org/bug-reports.html#small-is-beautiful-aim-for-a-single-document-with-10-lines.

If you have multiple files (and if it is absolutely required to have multiple files), please share as a Git repository.

R Python

````qmd
---
title: "Reproducible Quarto Document"
format: html
engine: knitr
---

This is a reproducible Quarto document.

{{< lipsum 1 >}}

```{r}
x <- c(1, 2, 3, 4, 5)
y <- c(1, 4, 9, 16, 25)

plot(x, y)

{#fig-placeholder}

{{< lipsum 1 >}}

The end after @fig-placeholder.

```

 ```
````qmd
---
title: "Reproducible Quarto Document"
format: html
engine: jupyter
---

This is a reproducible Quarto document.

{{< lipsum 1 >}}

```{python}
import matplotlib.pyplot as plt

x = [1, 2, 3, 4, 5]
y = [1, 4, 9, 16, 25]

plt.plot(x, y)
plt.show()
```

![An image]({{< placeholder 600 400 >}}){#fig-placeholder}

{{< lipsum 1 >}}

The end after @fig-placeholder.

Additionally and if not already given, please share the output of `quarto check` within a code block (_i.e._, using three backticks `` ```txt ``), see https://quarto.org/bug-reports.html#check.

Let's bring this back a whole bunch of steps. I entered my problem documentation issue because, I'm trying to go through the steps of the Quarto Getting Started documentation. That included downloading the CLI file and getting a successfully installed dialog (Quarto version 1.6.40, I think). I followed the steps up to the point of trying to Preview or Render the 'hello.ipynb' file supplied, and downloaded. Unfortunately, that file, supplied by Quarto displays an error when following the Getting Started steps. The TextEdit file is the only way I could find to display the contents of the 'hello.ipynb' file in order for someone to figure out what was needed to make it a valid JSON file. Obviously, something isn't clear in the Getting Started documentation or in the file supplied.