Strange error about pattern matching

[amichuda]

Bug description

I'm trying to figure out an error, but I can't get a sense of what it means at all. I'm using 0.9.603 in VSCode and Python on Windows.

This happens when I run preview on my .qmd file.

Starting python3 kernel...Done

Executing 'paper.ipynb'
  Cell 1/7...Done
  Cell 2/7...Done
  Cell 3/7...Done
  Cell 4/7...ERROR: 

None of the known patterns match for   omitted due to data restrictions.

Any idea what might be causing this?

here's my quarto check:

[✓] Checking Quarto installation......OK
      Version: 99.9.9
      Path: /home/am2497/quarto-cli/package/dist/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.9.7 (Conda)
      Path: /home/am2497/miniconda3/envs/uganda-uber/bin/python
      Jupyter: 4.9.1
      Kernels: minimod-env, python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.0.5
      Path: /home/am2497/miniconda3/envs/uganda-uber/lib/R
      LibPaths:
        - /home/am2497/miniconda3/envs/uganda-uber/lib/R/library
      rmarkdown: (None)

      The rmarkdown package is not available in this R installation.
      Install with install.packages("rmarkdown")

Checklist

• formatted your issue so it is easier for us to read?
• included a minimal, self-contained, and reproducible example?
• documented the quarto version you're running, by providing the output produced by quarto check in a terminal in your issue?
• documented the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
• documented which operating system you're running? If on Linux, please provide the specific distribution as well.
• upgraded to the latest version, including your versions of R, the RStudio IDE, and relevant R packages?

[jjallaire]

We'll need to see the source code of your .qmd file in order to help debug this further.

[cscheid]

I'm assuming this is the same issue as #1222, which is now fixed. Please let us know if the issue remains (and also do please provide that .qmd for reproduction).