ERROR: "No inspectable targets"-error when rendering PDF containing Mermaid diagram

Bug description

Hello,

Í'm using:

Latest version of R (4.2.2)
Latest version of Rstudio (2022.12.0 Build 353)
Latest Quarto (version 1.2.335)
Windows 10 Enterprise 22H2

When rendering a PDF from a .QMD-file containing a Mermaid diagram (https://quarto.org/docs/authoring/diagrams.html), my Rstudio gives the error "ERROR: No inspectable targets" and crashes (I'm unable to press stop).
In the past the same .QMD file rendered to PDF without any problem. Rendering to .HTML still works. The same error was recently reported by an Obsidian user: https://forum.obsidian.md/t/about-quarto-no-inspectable-targets-error/54757.

The .QMD-file i'm using can be found in the attached .ZIP (Github doesn't allow uploading QMD's directly, therefore I zipped).

Thanks for the good work!

Best,
Thomas

testdia.zip

Checklist

Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
Please format your issue so it is easier for us to read the bug report.
Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
Please document the operating system you're running. If on Linux, please provide the specific distribution.

Can you try with our 1.3 prereleases? I'm not on windows, but I can't reproduce the issue:

Dear Carlos,

After installing the 1.3.247 prerelease I still get the error when rendering a PDF (HTML works fine).

This time the error is more complex:

ERROR: No inspectable targets

Error: No inspectable targets
    at defaultTarget (file:///C:/Users/20003963/AppData/Local/Programs/Quarto/bin/quarto.js:55313:23)
    at Chrome._fetchDebuggerURL (file:///C:/Users/20003963/AppData/Local/Programs/Quarto/bin/quarto.js:55436:37)
    at async Chrome._start (file:///C:/Users/20003963/AppData/Local/Programs/Quarto/bin/quarto.js:55392:25)

I'm using the latest version of Google Chrome (110.0.5481.178 (Official build) (64-bits))

Best regards,
Thomas

@cderv

@cderv will know the details, but there are issues with Windows and headless Chrome.

I can reproduce with using Chrome browser from my system.

It works ok if I use chromium install with Quarto quarto install tools chromium - something must have changed with newest Chrome browser. I need to look into that.

Doc from the Zip to reproduce

---
title: "TestDiagram"
format: pdf
editor: visual
---

## Quarto


```{mermaid}
flowchart TD
    A[Christmas] -->|Get money| B(Go shopping)
    B --> C{Let me think}
    C -->|One| D[Laptop]
    C -->|Two| E[iPhone]
    C -->|Three| F[fa:fa-car Car]
```

@cscheid

Thank you very much for the quick help @cscheid and @cderv! quarto install tools chromium fixed the problem!

Best regards,
Thomas

@cscheid

@cscheid I reopened as I think it should be solves for any Chrome browser. Or do you consider our internal chromium to be the solution and we keep it closed ?

Here are some details on what is happening

We are retrieving the debugger url

quarto-cli/src/core/cri/deno-cri/chrome.js

Line 158 in e72f556

const url = await this._fetchDebuggerURL(options);

For that some targets are looked into , default being using defaultTarget function

quarto-cli/src/core/cri/deno-cri/chrome.js

Line 74 in e72f556

this.target = options.target || defaultTarget;

For the default targets we are calling

quarto-cli/src/core/cri/deno-cri/chrome.js

Lines 210 to 211 in e72f556

    
           const targets = await devtools.List(options); 
        
           const result = func(targets);

which query json/list endpoint, calling defaultTarget() on it.

I don't know yet why but with the Chrome browser version mentioned above, this will be empty

targets
(0) []

No targets to inspect.

This why code currently throw the error from

quarto-cli/src/core/cri/deno-cri/chrome.js

Lines 59 to 64 in e72f556

    
           target = target || backup; 
        
           if (target) { 
        
             return target; 
        
           } else { 
        
             throw new Error("No inspectable targets"); 
        
           }

Maybe we need to open a target if none exists (devtools.New()). FWIW, testing with chromium from quarto install, the targets to explore was about:blank

$ targets
[
  {
    description: "",
    devtoolsFrontendUrl: "/devtools/inspector.html?ws=localhost:9222/devtools/page/BA596C8DC87F7F55499F46F0EC363E27",
    id: "BA596C8DC87F7F55499F46F0EC363E27",
    title: "about:blank",
    type: "page",
    url: "about:blank",
    webSocketDebuggerUrl: "ws://localhost:9222/devtools/page/BA596C8DC87F7F55499F46F0EC363E27",
  },
]

@cscheid hope it helps you know what can be done. I'll look closer tomorrow about why we get this in Chrome now and maybe try the fix suggested above

and crashes (I'm unable to press stop).

I reproduce this also. We throw the error and then impossible to stop Quarto.

Create a new target for devtools if none if already available in open…

Fix no inspectable targets issue with Chrome Browser (#4696)

I can confirm this works now, with one small caveat ( that tripped me for a while). The required chromium triggers a "Chromium unexpectedly quit" menu on Mac. I guess this is a little process that runs, and then kills itself, but it triggers an ugly ( although, as I found out, inconsequential) message on Mac OSX Ventura.

@tomkom

@tomkom Oof, that's really no good. I'm on OSX Ventura as well and thought I had fixed this issue.

~~I'm no longer seeing the crash, but clearly the fix didn't stick.~~ I take it back; I see the crash once again.

Unfortunately, I can't seem to make the crash stop with Chromium on OS X Ventura.

So, we're changing the resolution order of browsers. If we find Google Chrome (for which the crash doesn't happen), then we use that directly, even if the user has installed Chromium.

We will still use Chromium if we don't find Google Chrome, but using Chromium will likely cause this crash.

I am getting the original problem "ERROR: No inspectable targets" rendering mermaid and dot diagram to PDF (HTML works OK).

Ubuntu 22.04.2
R 4.2.2
RStudio 2023.03-0 build 386
quarto 1.2.335
chrome installed
chromium installed
quarto install tools chromium installed

Let me know if there's something diagnostic I can do to get some more info on what's happening here.

Thanks.

quarto 1.2.335

You need to download and install a newer version of quarto.

@cscheid

Thanks @cscheid - that worked perfectly. I had misread the quarto version number and wrongly believed I was using the latest version.

Navigation Menu

Repository navigation

ERROR: "No inspectable targets"-error when rendering PDF containing Mermaid diagram #4653

Bug description

Checklist

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	const targets = await devtools.List(options);
	const result = func(targets);

	target = target \|\| backup;
	if (target) {
	return target;
	} else {
	throw new Error("No inspectable targets");
	}

ERROR: "No inspectable targets"-error when rendering PDF containing Mermaid diagram #4653

Description

Bug description

Checklist

Activity

cscheid commented on Mar 6, 2023

streepvaren commented on Mar 6, 2023

cscheid commented on Mar 6, 2023

cderv commented on Mar 6, 2023

streepvaren commented on Mar 6, 2023

cderv commented on Mar 6, 2023

tomkom commented on Mar 13, 2023

cscheid commented on Mar 13, 2023

cscheid commented on Mar 14, 2023

rgayler commented on Apr 2, 2023

cscheid commented on Apr 2, 2023

rgayler commented on Apr 2, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions