Bad YAML error in the presence of parse error

[cscheid]

---
title: Hello, world
format: html
---

```{r}
#| label: fig-foo
#| message: FALSE
#| echo:false
cat("HIIII")
```

[cscheid]

We don't print a stack trace here, not even when QUARTO_PRINT_STACK=true:

$ QUARTO_PRINT_STACK=true quarto render issue-9496.qmd
ERROR: YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key (issue-9496.qmd, 9:14)
 8: #| message: FALSE
 9: #| echo:false
                ~
10: cat("HIIII")

[gordonwoodhull]

I'm not able to repro. I added

 diff --git a/src/project/project-shared.ts b/src/project/project-shared.ts
index e45739f77..5d17abe6c 100644
--- a/src/project/project-shared.ts
+++ b/src/project/project-shared.ts
@@ -457,10 +457,14 @@ export async function projectResolveFullMarkdownForFile(
     flags: {} as RenderFlags,
   };
   try {
+    console.log('FOOO')
     const result = await expandIncludes(markdown, options, file);
     cache.fullMarkdown = result;
     cache.includeMap = options.state?.include.includes as FileInclusion[];
     return result;
+  } catch(xep) {
+    console.log(xep);
+    throw xep;
   } finally {
     temp.cleanup();
   }

I see 3

FOOO
[YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key (invalid-yaml.qmd, 9:14)
 8: #| message: FALSE
 9: #| echo:false
                ~
10: cat("HIIII")] {
  name: "YAMLException",
  reason: "can not read a block mapping entry; a multiline key may not be an implicit key",
  mark: {
    name: null,
    buffer: "label: fig-foo\nmessage: FALSE\necho:false\n",
    position: 41,
    line: 3,
    column: 0,
    snippet: " 1 | label: fig-foo\n 2 | message: FALSE\n 3 | echo:false\n 4 | \n-----^"
  },
  message: "can not read a block mapping entry; a multiline key may not be an implicit key (invalid-yaml.qmd, 9:"... 108 more characters
}

[cscheid]

I'm debugging that part of project-shared.ts with

  try {
    const result = await expandIncludes(markdown, options, file);
    cache.fullMarkdown = result;
    cache.includeMap = options.state?.include.includes as FileInclusion[];
    temp.cleanup();
    return result;
  } catch (e) {
    console.log("Exception:");
    temp.cleanup();
    console.log("\n");
    console.log(getStack());
    throw e;
  }

  // try {
  //   const result = await expandIncludes(markdown, options, file);
  //   cache.fullMarkdown = result;
  //   cache.includeMap = options.state?.include.includes as FileInclusion[];
  //   return result;
  // } finally {
  //   temp.cleanup();
  // }

(Specifically, I was disentangling await from try..finally to ensure I didn't have some other await bug lurking)

[cscheid]

A-ha! The first two stack traces are not the same, there were two different locations in render-files.ts.

[cscheid]

Ok, this is better:

$ quarto render issue-9496.qmd
ERROR: YAML Parse Error: block has incorrect key formatting (issue-9496.qmd, 9:4)
 8: #| message: FALSE
 9: #| echo:false
       ~~~~~~~~~~
10: cat("HIIII")
ℹ Is it possible you missed a space after a colon in the key-value mapping?

(cc @mine-cetinkaya-rundel, I think this error message should be more actionable now!)

[mcanouil]

What is "block"? 😅

[cscheid]

We use the term block at least once here: https://quarto.org/docs/reference/cells/cells-knitr.html#overview

[mcanouil]

• "executable code block" = "code cell" ("code chunk" by RMarkdown users), but I don't think we use anywhere "block" alone (Consistency needed CLI/WEB: "code cell" or "code chunk"? #6220).
• "code block" = (non executable) source code (https://quarto.org/docs/authoring/markdown-basics.html#source-code)